Feature your MCP

AGILEX Docs MCP

Official

Remote · MIT · Updated Nov 4, 2026

RegionGlobal

/AGILEX Docs MCP, explained

AGILEX Docs MCP is the official documentation server from AgileX Robotics (松灵机器人). It exposes the company's public knowledge base — user manuals, CAN 2.0B protocol references, firmware notes, SDK tech posts and after-sales FAQ — for products such as piper, pika, nero, ranger, limo, scout, bunker, hunter, tracer, umr, cobot_magic and aloha.

The server is read-only and requires no authentication: it is a single Streamable HTTP endpoint that any MCP client can use with just a URL. It is rate limited per IP (60 requests per minute, 3,000 per day).

The corpus covers 263 content pages across 26 public spaces (~3M characters, in Chinese and English), refreshed daily. The recommended workflow is search-then-locate-then-read: use search_docs to find the right manual, find_in_doc to jump to a specific passage such as a CAN frame table, and get_doc to read that section.

Results always include the original page URL so answers can be cited and verified.

The service only indexes publicly shared content and never authenticates, so internal documents cannot be reached. It performs lexical rather than semantic matching, does not inline images, and does not parse binary attachments such as PDFs.

AI-generated listing based on the project's public information. It may contain errors: check the original source.

/What AGILEX Docs MCP is for

Find the CAN baud rate and frame format for the piper arm before writing a control script, citing the manual URL
Search the after-sales FAQ for a ranger mini chassis error code and quote the troubleshooting steps
Look up firmware upgrade instructions for the pika robot
List all available manuals for the scout product family
Locate the pinout table inside a long manual without paging through the whole document

/What AGILEX Docs MCP can do once connected

What your assistant can call once connected.

ToolWhat it does
search_docsFull-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
find_in_docLocate 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
get_docRead 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 tr
list_docsList 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
list_spacesList 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,doc

/AGILEX Docs MCP: frequently asked questions

Do I need a key or an account?

No. It connects without a key.

Which assistants does it work with?

Claude, ChatGPT, Gemini, Grok

Which countries does it work in?

Any country.