AGILEX Docs

ai.agilex.service/docsVersion 1.8.0

Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only.

Status

Responds1032 msNov 14, 2026, 13:27 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:27 UTC
Latency: 1032 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://service.agilex.ai/agilex-docs/mcpResponds1032 msNov 14, 2026, 13:27 UTC

No sign-in

Claude Code

claude mcp add --transport http docs https://service.agilex.ai/agilex-docs/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: docs
Remote MCP server URL: https://service.agilex.ai/agilex-docs/mcp

Cursor

{
  "mcpServers": {
    "docs": {
      "url": "https://service.agilex.ai/agilex-docs/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"docs","type":"http","url":"https://service.agilex.ai/agilex-docs/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

5 tools

Tools of AGILEX Docs
	Description		Read-only	Idempotent	Open world
`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 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`` with a hint. Returns JSON: {doc_id,title,space,url,chars,query,count,returned, matched_terms,missing_terms,hits:[{offset,heading,score,matched,excerpt}], hint}. ``count`` is the total number of matched passages; ``returned`` is how many are in ``hits`` (capped by ``limit``). ``heading`` is the nearest heading above the passage; ``offset`` is absolute in the page body.	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 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`` with a hint. Returns JSON: {doc_id,title,space,url,chars,query,count,returned, matched_terms,missing_terms,hits:[{offset,heading,score,matched,excerpt}], hint}. ``count`` is the total number of matched passages; ``returned`` is how many are in ``hits`` (capped by ``limit``). ``heading`` is the nearest heading above the passage; ``offset`` is absolute in the page body.	No	Yes	Yes	No
`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). 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.	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). 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.	No	Yes	Yes	No
`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 with ``limit`` to decide whether to request the next page. There is no total field — use ``list_spaces`` for per-space counts.	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 with ``limit`` to decide whether to request the next page. There is no total field — use ``list_spaces`` for per-space counts.	No	Yes	Yes	No
`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}]}.	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}]}.	No	Yes	Yes	No
`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 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.	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 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.	No	Yes	Yes	No

Details

Registry status: Active
Published: Nov 13, 2026
Updated: Nov 13, 2026
Website: https://service.agilex.ai/agilex-docs/⁠ (opens in a new tab)
Repository: https://github.com/wgjsg/agilex-docs-mcp⁠ (opens in a new tab)
Categories (suggested): Knowledge and notesSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing