MCP server
NETTS publishes its documentation as an MCP server, so an AI agent can search these docs and the API specification itself instead of guessing or being fed a 700 KB text dump.
https://doc.netts.io/mcpThe server is read-only. It knows nothing about your account, keys or balance — only what is published on this site.
What the agent gets
| Tool | What it does |
|---|---|
search_docs | Full-text search over the documentation pages |
get_doc | Full Markdown of one page |
list_docs | Index of every page |
search_api | Search operations of NETTS API v2 |
get_endpoint | Parameters, schemas, responses and error codes of one operation |
get_openapi_schema | A reusable schema from the specification |
The blog is deliberately not indexed: those are articles for people, and for an agent they are noise.
Connect
Cursor and VS Code — use the Connect to Cursor and Connect to VS Code items in the menu at the top of any documentation page. They install the server in one click.
Claude Code
bash
claude mcp add --transport http netts-docs https://doc.netts.io/mcpAnything else — the transport is Streamable HTTP, no authentication:
json
{
"mcpServers": {
"netts-docs": {
"type": "http",
"url": "https://doc.netts.io/mcp"
}
}
}Without MCP
If your tool does not speak MCP, the same content is available as plain files:
/llms.txt— structured index of the documentation/llms-full.txt— the whole documentation in one file/openapi.yaml— the API specification- any page with
.mdappended, for example/api/v2/endpoints/order1h.md