AGILEX Docs
Official AGILEX robotics manuals, CAN protocol and firmware notes for coding assistants
Answered our latest tool-list check 3 hours ago with 5 tools. It will be marked verified after 3 successful checks in 7 days.
- Pricing
- Free
- Platforms
- API, Web
- Runs
- Remotely
- Version
- 1.8.0
- Listing updated
- 3 days ago
About AGILEX Docs
AGILEX Docs is a free MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
Aimed at engineers writing integration code for AGILEX robots, the server lets an assistant look up the manual instead of guessing baud rates, frame formats or pin definitions. It covers user manuals, CAN protocol, firmware notes and after-sales FAQ, and is read-only.
The tools list spaces and documents, search across them, fetch a document in chunks with a maximum character count and offset, and find text inside one document. The site is written in Chinese and has copy-paste setup for Claude Code, Codex, Cursor, VS Code, Cline, Continue, Claude Desktop and Cherry Studio.
The endpoint is hosted and shared by all clients, so nothing runs locally.
Install
Run in a terminal
claude mcp add --transport http docs https://service.agilex.ai/agilex-docs/mcpAdd to Settings → Connectors → Add custom connector
https://service.agilex.ai/agilex-docs/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"docs": {
"url": "https://service.agilex.ai/agilex-docs/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"docs": {
"type": "http",
"url": "https://service.agilex.ai/agilex-docs/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"docs": {
"serverUrl": "https://service.agilex.ai/agilex-docs/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"docs": {
"type": "http",
"url": "https://service.agilex.ai/agilex-docs/mcp"
}
}
}Tools this server provides (5)
Read directly from the server.
- search_docs
- Full-text search over the official AGILEX product documentation. Use this first for any question about AGILEX hardware: pinouts, CAN protocol details, baud rate, firmware upgrade, error codes, LED/beep meanings, installation, calibration, SDK usage. Args: query: Chinese or English keywords. Include the product name (piper / pika / nero / ranger / limo / scout / bunker / hunter / tracer / umr) plus
- find_in_doc
- Locate a passage *inside* one manual, without paging through it. Use this after ``search_docs`` whenever you need a specific table, command or error code rather than the whole page — including short documents, because manuals commonly open with a preamble and page 1 rarely answers a question. It returns the exact ``offset`` of each match, so one ``get_doc(doc_id, offset=...)`` lands on the right s
- get_doc
- Read one documentation page as Markdown. Call this with a ``doc_id`` returned by ``search_docs`` (or a slug such as ``ymZimX7JLe``). Manuals are often 20k-60k characters, so this tool paginates: if the reply has ``truncated: true`` and a ``next_offset``, call again with that ``offset`` to continue. Do not re-request the same offset. Args: doc_id: id from search_docs (also accepts the page slug). m
- list_docs
- List documented pages, optionally inside one space. Use when the caller wants an inventory ("what manuals exist for ranger") rather than an answer. Args: space: optional space slug or name fragment. limit: 1-300, default 100. offset: pagination offset, must be >= 0. Returns JSON: {space, count, offset, docs:[{doc_id,title,space,url,chars}]}. ``count`` is the number of docs in this page; compare it
- list_spaces
- List the public documentation spaces with page counts. Call this when the caller is unsure which product family a document belongs to, or to explain coverage. Returns JSON: {count, spaces:[{space,name,docs,chars}]}.
What it does
- Official robot docs
- Manuals, CAN protocol, firmware and FAQ from the maker.
- Paged reading
- Documents are fetched with size and offset limits.
- In-document search
- Find text inside a single document.
- Read-only
- Nothing can be changed through the server.
- Many client recipes
- Setup is documented for a long list of AI clients.
Good for
- Check the CAN frame format before writing control code
- Look up pin definitions for a robot base
- Find firmware upgrade notes
- Search the after-sales FAQ
Pricing
Free
Prices change. Check service.agilex.ai before you buy.
AGILEX Docs FAQ
Does it need a key?
None is shown; clients only need the endpoint URL.
What language is the documentation?
The site is in Chinese.
Can it change anything?
No, it is read-only.
Is AGILEX Docs free?
Yes. AGILEX Docs is free to use.
How do I add AGILEX Docs to Claude Code?
Run this command in your terminal: claude mcp add --transport http docs https://service.agilex.ai/agilex-docs/mcp
What are the best alternatives to AGILEX Docs?
The closest alternatives to AGILEX Docs are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.
Alternatives to AGILEX Docs

REA
MCP serverCLI and MCP server that lets coding agents reverse engineer apps and binaries
Runs locally- Open source
- 464K GitHub stars
- Developer tools

Codebase Memory
MCP serverLocal MCP server that builds a code knowledge graph for AI coding agents
Runs locally- Open source
- 48.7K GitHub stars
- Knowledge and memory

GitHub
MCP serverOfficial MCP server connecting AI assistants to GitHub repos, issues and workflows
Not checked yet- Remote
- Open source
- 34.5K GitHub stars
- Developer tools

Serena MCP: the IDE for your agent
MCP serverMCP toolkit giving coding agents symbol-level code retrieval and editing
Runs locally- Open source
- 31.5K GitHub stars
- Developer tools

XERJ
MCP serverLocal search engine for AI agents with cited answers over your code and docs
Runs locally- Open source
- 19.2K GitHub stars
- Knowledge and memory

Ouroboros
MCP serverSpec-first layer that pins requirements and verifies results of AI coding agent work
Runs locally- Open source
- 6.4K GitHub stars
- Developer tools