All servers / Docs / AGILEX Docs
AGILEX Docs
Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only.
Tested by ConnectATD Hosted serverTested 2026-11-22. Address: https://service.agilex.ai/agilex-docs/mcp · Registry name: ai.agilex.service/docs
Score 77 out of 100. Tested 2026-11-22.
Score breakdown
| Connects and stays up | 20 / 20 | |
|---|---|---|
| Tool descriptions | 12 / 20 | |
| Inputs explained | 0 / 15 | |
| Speed | 15 / 15 | |
| Safety basics | 15 / 15 | |
| Upkeep | 15 / 15 |
What we saw
- Connects and answers the MCP handshake: yes (2.2 seconds)
- Uses an encrypted (https) connection: yes
- Server reports itself as: agilex-docs 1.9.4
- Tools offered: 5 · Parameters with a plain description: 0 of 12
- One safe, read-only test call to
list_docs: worked (first call 0.8 seconds, repeat calls 0.5 seconds) - Official registry entry last updated: 2026-11-19
From the publisher
- No notes.
How hosted servers are graded
Hosted servers run on the publisher's own machines, so we cannot score downloads or install safety. We use six checks instead (connects and stays up 20, tool descriptions 20, inputs explained 15, speed 15, safety basics 15, upkeep 15). Speed is the first call to a safe, read-only tool (when a server marks none, the time to connect and list its tools), using a fresh request where we can so a saved answer cannot hide a slow one. We never call tools that write data or cost money. A server that needs a login or key is not graded. Full method.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions.
search_docs0 of 3 parameters describedFull-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 the concept, e.g. "piper CAN 波特率". limit: 1-25 results, default 8. space: optional space slug or name fragment to narrow the search, e.g. "agx-chassis-manual-cn-en" or "底盘使用手册". Returns JSON: {query, count, results:[{doc_id,title,space,url,score,chars,snippet}]}. ``count`` is the number of results in this reply (0-``limit``). Pages whose title carries 【未发】/【暂不对外】 are not offered for reading and never appear here — they are unpublished, not missing. ``doc_id`` is what ``get_doc`` expects.
find_in_doc0 of 3 parameters describedLocate 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 section. Prefer this over repeatedly calling ``get_doc`` with increasing offsets. Args: doc_id: id from ``search_docs`` (also accepts the page slug). query: the *concept*, not the product name — e.g. "波特率" or "急停 接线". Terms that already appear in this page's title are ignored, because ``search_docs`` picked the page by them; passing the product name again only adds noise. Generic words that appear in nearly every manual are down-weighted, so one distinctive term is enough. limit: 1-10 passages, default 5. Matching is OR, not AND: a passage is returned when it contains at least one term with enough weight. Terms that are absent from this page therefore do **not** force a zero result — check ``missing_terms`` to see which of your words this page never mentions, and ``matched_terms`` for the ones it does. A query made only of stop words (or nothing) returns ``count: 0``
get_doc0 of 3 parameters describedRead 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). max_chars: characters per call, default 20000, max 120000. offset: start position, default 0. Returns JSON: {doc_id,title,space,url,chars,offset,returned,max_chars, truncated,next_offset,updated_at,content}. Always cite ``url``. If the page has no body (folder or unwritten page), the reply has ``empty: true`` and a hint — do not retry with other offsets. A page whose title marks it unpublished returns ``unpublished: true`` with empty content; that is a publication decision, not a missing document.
list_docs0 of 3 parameters describedList 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 with ``limit`` to decide whether to request the next page. There is no total field — use ``list_spaces`` for per-space counts.
list_spacesno parametersList 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}]}.
Tested by ConnectATD. Spotted a mistake? Tell us.