PolyAI Docs

ai.poly由 poly.ai 發布官方發布者v1.0.0更新於 Nov 19, 2026

Search the PolyAI docs, including the Dialog-RSN-1 realtime voice API. No API key needed.

發布方自己的服務:PolyAI Builder MCP

已驗證Streamable HTTP可網頁執行知識與記憶開發者工具

概覽

AI 產生的概覽

遠端 MCP 伺服器,讓助理搜尋並閱讀 PolyAI 平台的公開文件,包含 API 參考與 OpenAPI 規格。

可以做什麼
  • 在 PolyAI 平台知識庫中搜尋指南、程式碼範例與 API 參考
  • 在僅含文件頁面與 OpenAPI 規格的虛擬記憶體檔案系統上執行唯讀的類 shell 查詢
  • 透過意見回饋工具向文件團隊回報文件問題
適用情境
適合回答關於 PolyAI 平台及其 Dialog-RSN-1 即時語音 API 的問題、查找實作細節,或以最新文件取代模型記憶時使用。
執行需求
需要連線至 docs.poly.ai 的遠端 streamable HTTP 端點;未宣告 API 金鑰、環境變數或標頭。需要網路連線。
安裝前請注意
submit_feedback 工具會將回報傳送給 PolyAI 文件團隊,回饋內容請勿包含密鑰或私密資料。除此之外伺服器為唯讀,僅限已發布的網站內容,不提供私有或需驗證內容的存取。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 PolyAI Docs,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ai.poly%2Fdocs-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "polyai-docs": {
      "type": "http",
      "url": "https://docs.poly.ai/mcp"
    }
  }
}

工具

3

search_poly_ai_platform

Search documentation

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`).

輸入參數query必填

query_docs_filesystem_poly_ai_platform

Query documentation filesystem

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 layout - `rg -il "rate limit" /` — find all files mentioning "rate limit

輸入參數command必填

submit_feedback

Submit documentation feedback

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.

輸入參數path必填feedback必填

版本歷史

1
  1. v1.0.0最新Nov 19, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。

其他 Poly 整合