Docs MCP
Eight tools let an assistant read about OneSource: search the docs, list endpoints, look up parameters and pricing, find endpoints by use case. They are free, read-only, and need no credential.
@one-source/mcp already includes them, so if you have the main server installed there is nothing else to add. They answer "how do I use the OneSource REST API?" while its chain tools answer "what's the current ETH balance of vitalik.eth?"
@one-source/docs-mcp ships the same eight on their own, for when you want documentation help and nothing else: no auth, no payment, no live data, no wallet.
| Package | What it does | Auth |
|---|---|---|
@one-source/mcp | Calls live OneSource endpoints, and searches the docs | API key, x402, or MPP (the documentation tools stay free) |
@one-source/docs-mcp | Searches OneSource docs offline | None |
Installing the docs server on its own
Reach for this when the assistant should read about OneSource without being able to call the chain or spend anything.
Hosted endpoint (zero setup)
The docs MCP is also hosted as a stateless HTTP endpoint. Point any MCP client that supports HTTP transport at:
https://docs.onesource.io/api/mcp
No install, no auth. Best path for clients that support remote MCP servers.
Local install
Claude Code:
claude mcp add onesource-docs -- npx -y @one-source/docs-mcp
Claude Desktop / Cursor / Windsurf:
{
"mcpServers": {
"onesource-docs": {
"command": "npx",
"args": ["-y", "@one-source/docs-mcp"]
}
}
}
VS Code:
{
"servers": {
"onesource-docs": {
"command": "npx",
"args": ["-y", "@one-source/docs-mcp"]
}
}
}
Any MCP client (stdio): npx -y @one-source/docs-mcp.
Tools
| Tool | Purpose |
|---|---|
1s_search_docs | Keyword search across all OneSource docs |
1s_get_api_overview | Operation counts, tags, networks, sample endpoints |
1s_list_endpoints | List endpoints (optional tag filter): method, path, price, summary |
1s_get_endpoint_reference | Full reference for one endpoint: parameters, request body, example response, curl |
1s_search_use_cases | Find endpoints by natural-language description |
1s_list_networks | Supported networks |
1s_get_payment_info | x402 / MPP protocols, prices, pay-to addresses |
1s_get_authentication_guide | Bearer / x402 / MPP auth: code examples |
The data is bundled from the committed OpenAPI snapshot and the Markdown sources of this site. Publishing is gated on both bundled copies being current, and there are no network calls at runtime.
Registering it alongside the main server
@one-source/mcp carries these eight tools already, so most setups need only that one entry. Registering both is still valid, and they do not conflict, but your assistant then sees each documentation tool twice:
{
"mcpServers": {
"onesource": {
"command": "npx",
"args": ["-y", "@one-source/mcp@latest"],
"env": { "ONESOURCE_API_KEY": "sk_…" }
}
}
}
Also see
- Tool reference: every tool the main server exposes, documentation tools included.
- AI editor setup guide: uses a generic
mcpdoc-based docs server readingllms.txt. Lighter-weight; trades the structured tools above for plain keyword search.