Connect Metabind Docs and your agent gets 3 tools, among them query_docs_filesystem_metabind, search_metabind, submit_feedback. It answers at https://docs.metabind.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 27 September 2026; the last check, on 12 November 2026, succeeded.
Search and read the Metabind documentation: MCP Apps, BindJS, the SDKs, the CLI, and the APIs.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
query_docs_filesystem_metabind | Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Metabind documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, Inputs: command |
search_metabind | Search across the Metabind knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Metabind, find specific documentation, understand how features work, or Inputs: query |
submit_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 — n Inputs: path, feedback |
Every block below points at https://docs.metabind.ai/mcp. Pick your client and copy.
claude mcp add --transport http metabind-docs https://docs.metabind.ai/mcp
{
"mcpServers": {
"metabind-docs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://docs.metabind.ai/mcp"]
}
}
}{
"mcpServers": {
"metabind-docs": {
"url": "https://docs.metabind.ai/mcp"
}
}
}{
"servers": {
"metabind-docs": {
"type": "http",
"url": "https://docs.metabind.ai/mcp"
}
}
}{
"context_servers": {
"metabind-docs": {
"url": "https://docs.metabind.ai/mcp"
}
}
}{
"mcpServers": {
"metabind-docs": {
"serverUrl": "https://docs.metabind.ai/mcp"
}
}
}{
"mcpServers": {
"metabind-docs": {
"url": "https://docs.metabind.ai/mcp"
}
}
}name: Metabind Docs
version: 0.0.1
schema: v1
mcpServers:
- name: Metabind Docs
type: streamable-http
url: https://docs.metabind.ai/mcp{
"mcpServers": {
"metabind-docs": {
"httpUrl": "https://docs.metabind.ai/mcp"
}
}
}{
"mcpServers": {
"metabind-docs": {
"type": "http",
"url": "https://docs.metabind.ai/mcp"
}
}
}{
"mcpServers": {
"metabind-docs": {
"url": "https://docs.metabind.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fdocs.metabind.ai%2Fmcp&type=streamable_http&id=metabind-docs&name=Metabind%20Docs
It answered our last check on 12 November 2026 in 282 ms. Over 4 checks since 27 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by metabind.ai and served from docs.metabind.ai, the vendor's own domain: https://docs.metabind.ai/mcp.
3, as returned by the server's own tools/list on 17 November 2026: query_docs_filesystem_metabind, search_metabind, submit_feedback.
It answered our last check on 12 November 2026 in 282 ms. Over 4 checks since 27 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://docs.metabind.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.metabind. Endpoint host: docs.metabind.ai. ARD identifier: urn:air:ai.metabind:mcp:docs.
First indexed 27 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.