Metabind Docs
Search and read the Metabind documentation: MCP Apps, BindJS, the SDKs, the CLI, and the APIs.
- 1.0.0
- Version
- remote
- Transport
- 3
- Tools
Security review
Review passedReviewed 1d ago.
- tools: 3 tools scanned
- metadata: scanned
No findings.
Tools (3)
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 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_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, 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
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 — not for product support requests or feedback about this tool or assistant.