natural-docs-mcp
Provides read-only tools to search, read, and look up Natural API documentation from an AI agent, enabling documentation lookup without credentials.
README
natural-docs-mcp
Search, read, and look up Natural API documentation from your AI agent.
Unofficial. Not affiliated with, endorsed by, or operated by Natural AI, Inc. A community companion to Natural's official operational MCP. It reads Natural's own published docs — it moves no money and needs no credentials.
Live endpoint: https://natural-docs-mcp.jsharma103.workers.dev/mcp
Why
Natural's official MCP server exposes 24 operational tools (payments, wallets, agents,
transfers) but no way to read the docs. An agent mid-integration ends up fetching raw
llms.txt over HTTP — which fails on hosts without web access, burns context on full-page
dumps, and offers no ranked search.
This server adds the missing documentation surface: four read-only tools, one hosted URL,
nothing to install. Docs are fetched live from docs.natural.com (cached 15 min), so
answers are never stale and no snapshot is redistributed.
Tools
| Tool | Answers | Notes |
|---|---|---|
list_docs |
"What docs exist?" | Sections → pages, a table of contents (~2KB) |
search_docs |
"Which page covers X?" | BM25 ranking, returns snippets not full pages |
read_doc |
"Give me that page." | Fetches a page as markdown by slug or URL |
lookup_endpoint |
"Exact shape of this endpoint?" | OpenAPI lookup; detail=true returns pruned parameter/request/response schemas |
Install
No install, no auth — add one URL as a custom MCP server.
Claude Code
claude mcp add --transport http natural-docs https://natural-docs-mcp.jsharma103.workers.dev/mcp --scope user
Then /mcp to confirm natural-docs is connected. Try: "Search the Natural docs for idempotency."
Claude (claude.ai / Desktop)
Sidebar → Customize → Connectors → Add custom connector. Name Natural Docs,
URL https://natural-docs-mcp.jsharma103.workers.dev/mcp.
Cursor
Settings → Tools & MCPs → New MCP Server, then merge:
{
"mcpServers": {
"natural-docs": { "url": "https://natural-docs-mcp.jsharma103.workers.dev/mcp" }
}
}
How it works
Three published, machine-readable sources are fetched at runtime and cached in-isolate:
docs.natural.com/llms.txt— the section/page index (list_docs)docs.natural.com/llms-full.txt— the full corpus, 164 pages, chunked per page and indexed with minisearch BM25 (search_docs)docs.natural.com/api-reference/openapi.json— lazily parsed into an operations index; a single operation is pruned on demand — examples stripped,$refs resolved one level (lookup_endpoint)
No database, no vector store, no embeddings, no persistence. Just their own artifacts, indexed in memory.
Architecture
Layered so the documentation logic is portable, not welded to the host:
src/
core/ parsing + search + OpenAPI pruning — platform-free (web-standard fetch only)
tools/ the four tools as a transport-agnostic registry (zod shape + JSON Schema + handler)
entry/
worker.ts Cloudflare Worker — stateless Streamable HTTP MCP (the live deployment)
node.ts stdio + official MCP SDK — offline/local fallback and test target
core/ and tools/ carry no platform dependency; the entry files are thin adapters. The
Worker is stateless (no Durable Objects, no sessions) — each POST carries one JSON-RPC
message, handled inline.
Develop
npm install
npm run build # tsc -> dist/ (noEmitOnError gate)
npm run smoke # spawn the stdio server, exercise all 4 tools + golden queries
npm start # run the stdio server locally
npx wrangler dev # run the Worker locally
npx wrangler deploy # deploy the Worker
npm run smoke is the CI gate: it calls every tool and requires each golden integration
query (idempotency, payment requests, vault, limits, errors) to surface the right page in
the top 3.
See docs/EXAMPLES.md for real request/response transcripts.
Limitations
lookup_endpointdetail returns a representative subset of responses (primary 2xx + one error); other codes are listed underx-omitted-response-codes. Output is compact JSON capped at 14000 chars — enough for every current Natural operation.- First request after a cold start or cache expiry re-fetches the corpus/spec.
License
MIT © 2026 Jay Sharma. "Natural" and related marks belong to Natural AI, Inc.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。