Docs MCP (companion)
The runtime @one-source/mcp lets your assistant call OneSource: make real Ethereum reads, run paid endpoints, fetch live data.
A separate package, onesource-docs-mcp, lets the assistant read about OneSource: search the docs, list endpoints, look up parameters and pricing, find endpoints by use case. No auth, no payment, no live data.
Most people want both. They complement each other: the docs MCP answers "how do I use the OneSource REST API?", the runtime MCP answers "what's the current ETH balance of vitalik.eth?"
| MCP | Package | What it does | Auth | Tools |
|---|---|---|---|---|
| Runtime | @one-source/mcp | Calls live OneSource endpoints | API key or x402 | 30 |
| Docs | onesource-docs-mcp | Searches OneSource docs offline | None | 8 |
When you only want the docs MCP
If you only want documentation help (no live data, no payments), install just the docs MCP.
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 onesource-docs-mcp
Claude Desktop / Cursor / Windsurf:
{
"mcpServers": {
"onesource-docs": {
"command": "npx",
"args": ["-y", "onesource-docs-mcp"]
}
}
}
VS Code:
{
"servers": {
"onesource-docs": {
"command": "npx",
"args": ["-y", "onesource-docs-mcp"]
}
}
}
Any MCP client (stdio): npx onesource-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 at publish time from the live OpenAPI spec and the Markdown sources of this site: no network calls at runtime.
Running both
You can register both MCPs side-by-side under different names; they don't conflict. The runtime MCP's tools are the blockchain tools (1s_*_live, 1s_network_info, 1s_tx_receipt, …); the docs MCP's are prefixed 1s_search_* / 1s_get_* / 1s_list_*, so your assistant can easily pick the right one.
{
"mcpServers": {
"onesource": {
"command": "npx",
"args": ["-y", "@one-source/mcp@latest"],
"env": { "ONESOURCE_API_KEY": "sk_…" }
},
"onesource-docs": {
"command": "npx",
"args": ["-y", "onesource-docs-mcp"]
}
}
}
Also see
- AI editor setup guide: uses a generic
mcpdoc-based docs server readingllms.txt. Lighter-weight; trades the structured 8-tool surface above for plain keyword search.