Skip to main content
The documentation MCP server searches these docs and reads the API guides. Use it when an agent writes an integration or checks setup. It needs no Arcmira sign-in or key. It does not query videos; that is the Arcmira MCP server, and you can connect both. Add it to your MCP client as arcmira-docs:
Then ask: “Read the Arcmira API docs and show me how to search YouTube transcripts with timestamps.”

Connect from an agent framework

Each recipe connects over Streamable HTTP and either calls docs search once or builds the toolset for your agent. None makes a model call or needs an Arcmira key. Each exposes only two tools, search_arcmira_api and query_docs_filesystem_arcmira_api, and leaves out the tool that submits documentation feedback. The filesystem tool reads the documentation service, not your local files. Keep the client or context open until the agent finishes, streamed calls included. Every recipe passed live tool discovery and documentation search with the versions it names. Model inference was not tested. Running an agent incurs your model provider’s usual charges, and docs access does not grant video research. For YouTube transcript search from a framework, see CLI and SDKs.
Tested with @ai-sdk/mcp 2.0.60 and zod 4.6.5. Install those packages in your AI SDK project.
Pass tools to your generateText call inside the try block. The explicit schemas expose only the two read tools. See the AI SDK MCP guide for model setup and streaming cleanup.