MCP100 verdict
Not currently recommended. First-party or well-evidenced implementation identity, meaningful task value, maintained setup evidence, and no material admission veto were found in reviewed sources.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Shortlist evidence is sufficient for identity, setup and task value; authenticated runtime tool-schema measurement and exhaustive security certification remain out of scope.
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Evidence scope
534 MCP repository stars
6.4k package downloads / 30 days
Repository identity: anyproto/anytype-mcp
Package identity: @anyproto/anytype-mcp · version 2.0.1
Stars observed October 20, 2026 · Downloads observed October 20, 2026
Current first-party Anytype MCP implementation repository with server source code.
Exact MCP-specific npm package identity verified against the current first-party implementation.
Publisher activity observed October 20, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-20
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
{"command":"npx","args":["-y","@anyproto/anytype-mcp"],"env":{"OPENAPI_MCP_HEADERS":"{\"Authorization\":\"Bearer <YOUR_API_KEY>\", \"Anytype-Version\":\"2025-11-08\"}"}}Capability
Anytype MCP is Anytype’s official local MCP wrapper over the Anytype API, dynamically exposing supported knowledge-base operations from the local OpenAPI document. The MCP can create, edit and delete knowledge-base objects. API keys are sensitive; use etags/If-Match for concurrency-sensitive writes and keep the local API endpoint and bearer key private.
Tools are generated from the Anytype OpenAPI document selected at MCP startup and can change with Anytype API version; no stable exact total is asserted.
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
@anyproto/anytype-mcp
Reviewed access
Reviewed sources
Related reviewed MCPs
Retrieve current library and framework documentation for coding agents.
Choose this instead if
Choose Context7 MCP instead if current library and API documentation inside coding agents.
Retrieve current library and framework documentation for coding agents.
Explore Tableau sites, workbooks, data sources, metadata, and governed analytics.
Choose this instead if
Choose tableau instead if business-intelligence discovery and analysis using authorized Tableau content.
Explore Tableau sites, workbooks, data sources, metadata, and governed analytics.
Search Hugging Face Hub resources and use explicitly enabled Jobs, sandboxes, and community Space tools.
Choose this instead if
Choose Hugging Face MCP instead if searching models, datasets, Spaces, papers, and Hugging Face documentation.
Search Hugging Face Hub resources and use explicitly enabled Jobs, sandboxes, and community Space tools.
Anytype is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
From the publisher README
Original client setup and configuration retained from the publisher documentation.
Publisher-documented clients
These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.
Create new buttonYou can also get your API key using the command line:
npx -y @anyproto/anytype-mcp get-key
Add the following configuration to your MCP client settings after replacing <YOUR_API_KEY> with your actual API key:
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": ["-y", "@anyproto/anytype-mcp"],
"env": {
"OPENAPI_MCP_HEADERS": "{\"Authorization\":\"Bearer <YOUR_API_KEY>\", \"Anytype-Version\":\"2025-11-08\"}"
}
}
}
}
Tip: After creating an API key in Anytype, you can copy that ready-to-use configuration snippet with your API key already filled in from the API Keys section.
Run this command to add the Anytype MCP server after replacing <YOUR_API_KEY> with your actual API key:
claude mcp add anytype -e OPENAPI_MCP_HEADERS='{"Authorization":"Bearer <YOUR_API_KEY>", "Anytype-Version":"2025-11-08"}' -s user -- npx -y @anyproto/anytype-mcp
If you prefer to install the package globally:
npm install -g @anyproto/anytype-mcp
{
"mcpServers": {
"anytype": {
"command": "anytype-mcp",
"env": {
"OPENAPI_MCP_HEADERS": "{\"Authorization\":\"Bearer <YOUR_API_KEY>\", \"Anytype-Version\":\"2025-11-08\"}"
}
}
}
}
By default, the server connects to http://127.0.0.1:31009. For anytype-cli (port 31012) or other custom base URLs, set ANYTYPE_API_BASE_URL:
MCP Client (Claude Desktop, Cursor, etc.):
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": ["-y", "@anyproto/anytype-mcp"],
"env": {
"ANYTYPE_API_BASE_URL": "http://localhost:31012",
"OPENAPI_MCP_HEADERS": "{\"Authorization\":\"Bearer <YOUR_API_KEY>\", \"Anytype-Version\":\"2025-11-08\"}"
}
}
}
}
Claude Code (CLI):
claude mcp add anytype \
-e ANYTYPE_API_BASE_URL='http://localhost:31012' \
-e OPENAPI_MCP_HEADERS='{"Authorization":"Bearer <YOUR_API_KEY>", "Anytype-Version":"2025-11-08"}' \
-s user -- npx -y @anyproto/anytype-mcp
git clone https://github.com/anyproto/anytype-mcp.git
cd anytype-mcp
bun install
bun run build
bun link
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
The Anytype MCP Server is a Model Context Protocol (MCP) server enabling AI assistants to seamlessly interact with Anytype's API through natural language.
It bridges the gap between AI and Anytype's powerful features by converting Anytype's OpenAPI specification into MCP tools, allowing you to manage your knowledge base through conversation.
Here are some examples of how you can interact with your Anytype:
The server loads one OpenAPI document at startup. With the standard configuration it tries /v2/docs/openapi.json first. If that endpoint returns 404 or 410, it falls back to /docs/openapi.json on the same server, where older apps serve v1. This selects v2 whenever available while supporting apps that only have the legacy API:
"args": ["-y", "@anyproto/anytype-mcp"]
To explicitly use the legacy v1 API, select its versioned spec:
"args": ["-y", "@anyproto/anytype-mcp", "run", "http://127.0.0.1:31009/v1/docs/openapi.json"]
The versioned /v2/docs/openapi.json URL also remains available for explicitly selecting v2.
Explicit spec URLs and local files are used exactly as supplied, without fallback. Authentication failures, server errors, connection failures, and malformed JSON also fail startup instead of selecting another API. The wrapper uses the routes declared in the selected document without rewriting their version prefixes.
Discovery runs once per MCP process. Tool calls reuse the parsed specification and HTTP client without fetching OpenAPI again. Restart the MCP server after updating Anytype to discover a newly available API version; no persistent spec cache is used.
Tool descriptions contain operation guidance; API errors are returned when calls fail, with isError: true, HTTP status when available, and the API's code, message, issues, and hints.
The server names its own operations by OpenAPI operationId in the prose it serves. In the MCP tool listing and in the field descriptions of a get_schema or get_op_schema response, those names are re-spelled as this wrapper's tool names (list_properties becomes API-list-properties). A repair hint is different: the server spells each operation it names as a REST route and lists it as a typed see_also reference, so the wrapper replaces that route text with the tool name and arguments, and annotates the reference with tool and args. Literal values are never rewritten: enum and example values, op names, endpoint strings and output schemas keep the server's spelling, and so do the OpenAI and Anthropic tool exports, which name tools by operationId.
Successful v1 object creation, updates, deletion, and chat creation return a compact object receipt with its ID, space ID, name, archive state, and type identity when available. The wrapper omits echoed markdown, snippets, property values, icons, and full type definitions. It preserves warnings, generated IDs, and etag/retry metadata. Read the object to retrieve its content when needed. v2 already returns compact create/edit receipts, which are passed through unchanged apart from their warnings, whose hints are re-spelled and whose references gain tool and args; reads, searches, and errors also keep their full API responses.
The shared tool policy controls inputs and request routing:
Authorization and Anytype-Version come from OPENAPI_MCP_HEADERS.expected_etag maps to If-Match. Use the etag from a previous read to prevent overwriting a changed object. The wrapper does not retry a failed precondition or remove it. Response etags are returned in a separate request_metadata text block when available.request_key maps to Idempotency-Key on endpoints that declare that header. Omit it for a new write; the wrapper generates a unique key and returns it in request_metadata or an error's request_key. Reuse it only to retry the same write. Separate calls get different generated keys, even with identical documents. There are no automatic retries. A global Idempotency-Key in OPENAPI_MCP_HEADERS is rejected.If-Match and Idempotency-Key argument names. They are not advertised alongside the new names. Conflicting alias values are rejected.dry_run, create_missing_options, and schema discovery remain available.auth_whoami remains available for inspecting the current credential's permissions; its response does not contain the bearer token.path, filename, media_type, and size. The path is local to the machine/container running MCP. Successful files remain there until removed or cleaned up by the operating system; interrupted downloads are removed. Range and cache headers are not model inputs.Known inputs with HTTP meanings are matched by parameter location, so a document's own fields are preserved. Open-ended JSON documents use the body argument. Objects with declared fields use flat arguments. The existing omission of flattened filters fields and the FilterExpression schema fallback remain separate limitations; this cleanup does not restore filter-schema support.
Duplicate final tool names fail startup with both routes identified. Select separate v1/v2 specs instead of merging operations with overlapping names.
Set ANYTYPE_MCP_DEBUG=1 for concise operation names, response status, and timing on stderr. Arguments, authorization headers, payloads, and entire operation tables are not logged.
bun run measure-tools
# Or inspect a different local OpenAPI document:
bun run measure-tools ./path/to/openapi.json
The default command compares fixed v1 and v2 fixtures. It reports tool count, serialized characters, and UTF-8 bytes, not model-specific token counts.
Thank you for your desire to develop Anytype together!
❤️ This project and everyone involved in it is governed by the Code of Conduct.
🧑💻 Check out our contributing guide to learn about asking questions, creating issues, or submitting pull requests.
🫢 For security findings, please email security@anytype.io and refer to our security guide for more information.
🤝 Follow us on Github and join the Contributors Community.
Made by Any — a Swiss association 🇨🇭
Licensed under MIT.