PolyAI Docs
Server Details
Search the PolyAI docs, including the Dialog-RSN-1 realtime voice API. No API key needed.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
search_poly_ai_platform and query_docs_filesystem_poly_ai_platform both retrieve documentation content, which creates a real risk of misselection on first call. However, the descriptions explicitly carve out the division of labor (semantic/conceptual search vs. exact regex, structural exploration, and full-page reads), so an attentive agent can tell them apart.
All names are lowercase snake_case with a leading verb, which is readable, but the pattern is inconsistent: one tool embeds a redundant '_poly_ai_platform' site suffix while another stacks 'query_docs_filesystem_poly_ai_platform'. The convention is recognizable but not clean verb_noun throughout.
Three tools (semantic search, filesystem read/search, feedback) is a lean but sensible surface for a read-only documentation server. Nothing feels padded, though the set is on the thin side and leans on one tool doing many jobs.
Search, page reading, structural listing (tree/ls), OpenAPI spec access, and a feedback channel cover the documentation-consumption lifecycle well. The only quirk is that page retrieval is folded into a shell-emulation tool rather than exposed directly, which agents must learn from the description rather than from the tool list.
Available Tools
3 toolsquery_docs_filesystem_poly_ai_platformQuery documentation filesystemARead-onlyIdempotentInspect
Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at / that contains ONLY the PolyAI Platform documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.
This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its .mdx path to head or cat — a page at the URL path /some/page lives at /some/page.mdx. To search the docs with exact keyword or regex matches, use rg. To understand the docs structure, use tree or ls.
Paths are specific to this site — never guess them. Discover real paths with tree / -L 2, ls /, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use rg -il "keyword" / to find where it is covered.
Workflow: Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path.
Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, jq, plus basic text utilities. No writes, no network, no process control. Run --help on any command for usage.
Each call is STATELESS: the working directory always resets to / and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with && or pass absolute paths (e.g., cd /some-directory && ls or ls /some-directory). Do NOT assume that cd in one call affects the next call.
Examples (replace the placeholder paths with real ones from tree or search):
tree / -L 2— see the top-level directory layoutrg -il "rate limit" /— find all files mentioning "rate limit"rg -C 3 "apiKey" /some-directory/— show matches with 3 lines of context around each hithead -80 /some/page.mdx— read the top 80 lines of a specific pagehead -80 /page-one.mdx /page-two.mdx /section/page-three.mdx— read multiple pages in one callcat /some/page.mdx— read a full page when you need everythingcat /openapi/api-reference/agents/openapi.json | jq '.paths | keys'— list OpenAPI endpoints
OpenAPI specs for this site are mounted under /openapi; run find /openapi -type f to list them. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication.
Output is truncated to 30KB per call. Prefer targeted rg -C or head -N over broad cat on large files. To read only the relevant sections of a large file, use rg -C 3 "pattern" /path/file.mdx. Batch multiple file reads into a single head or cat call whenever possible.
When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the .mdx extension. For example, /some/page.mdx becomes /some/page.
Inputs: command (required).
search_poly_ai_platformSearch documentationARead-onlyIdempotentInspect
Search across the PolyAI Platform knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about PolyAI Platform, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to head or cat the page path (append .mdx to the path returned from search — e.g. a result at /some/page is read with head -200 /some/page.mdx).
Inputs: query (required).
submit_feedbackSubmit documentation feedbackAInspect
Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.
Inputs: path (required), feedback (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read-only search over the Vocenya AI receptionist API docs and endpoints, with code samples.
Search the eSignStack e-signature API, webhook and MCP docs. Public and read-only, no sign-in.
21Search the Cerebrium docs: deployment, cerebrium.toml, hardware, endpoints. Also sends feedback.
Search Modellix documentation for model APIs, request schemas, and usage guides.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables searching and retrieving Reflex documentation, including full-text search, code examples, error analysis, changelog, migration guides, API reference, component props, and recipes.143MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and ask questions across versioned service documentation, retrieve documents and diffs, and find related docs with cited answers over Streamable HTTP, SSE, or stdio.296 npmMIT
- AlicenseAqualityBmaintenanceLive, ranked search across any number of llms.txt documentation sites - Strands, Kiro, the AWS guides, and whatever you add at runtime.756 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to search and retrieve Holochain documentation, including developer guides, HDK functions, and HDI API references.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.