Anytype MCP

What anytype-mcp MCP server does

The anytype-mcp MCP server exposes Anytype API operations through the Model Context Protocol. It lets an MCP-compatible assistant interpret natural-language requests and use generated tools to work with an Anytype knowledge base.

Supported areas include global and space search, spaces and members, objects and lists, properties and tags, and types and templates. The README shows workflows such as creating a space, adding task objects, assigning a task, setting due dates, and creating a collection containing those tasks.

The server is intended for developers who want an assistant to read or modify Anytype data through a conversational interface rather than implementing direct API calls in an application.

How it works

The project converts Anytype’s OpenAPI specification into MCP tools. An MCP client starts the package as a local process, and the server sends requests to the Anytype API. The default API base URL is http://127.0.0.1:31009.

Authentication is passed as a JSON string in the OPENAPI_MCP_HEADERS environment variable. The documented value includes an Authorization bearer token and an Anytype-Version header set to 2025-11-08. The API key can be created in Anytype under App Settings, in the API Keys section. The package also provides a get-key command for obtaining a key through the CLI.

Setup and configuration

Install and run the package with npx:

npx -y @anyproto/anytype-mcp

Configure the MCP client with the package as the command and provide OPENAPI_MCP_HEADERS in its environment. Replace the placeholder bearer token with a real Anytype API key before starting the client. The README provides configuration examples for Claude Desktop, Cursor, Windsurf, Raycast, and Claude Code, and includes direct installation links for Cursor and other clients.

For a different API endpoint, set ANYTYPE_API_BASE_URL. The README gives http://localhost:31012 as an example for anytype-cli. Source installation requires Bun: clone the repository, run bun install, and build with bun run build.

Tools and capabilities

The anytype-mcp MCP server covers these documented capability groups:

• Search across Anytype or within a space
• Work with spaces and their members
• Create and manage objects and lists
• Use properties and tags
• Work with types and templates

These capabilities can be combined in a single conversational workflow. For example, an assistant can create a space, add task objects to it, assign a task, apply due dates, and place the tasks in a collection.

Limitations and notes

The server requires an Anytype API key and access to the configured Anytype API endpoint. The default endpoint is local, so the Anytype application or another compatible local API service must be available at that address. If the API is exposed on another port or URL, configure ANYTYPE_API_BASE_URL rather than relying on the default.

The README documents the Anytype-Version request header as 2025-11-08; clients should preserve the complete header JSON format shown in the setup examples. The project is licensed under MIT.