Anytype MCP Server
Official Anytype MCP server: an agent searches, creates and edits objects, lists and types in your knowledge base
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Creates, changes and deletes objects in your Anytype knowledge base
- Handles an API key passed in the Authorization header
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/anytype-mcp-serverDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run in a terminal
claude mcp add --transport stdio --env 'OPENAPI_MCP_HEADERS=<your OPENAPI_MCP_HEADERS>' anytype -- npx -y @anyproto/anytype-mcpOr add to the file .mcp.json, in the project
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"anytype","type":"stdio","command":"npx","args":["-y","@anyproto/anytype-mcp"],"env":{"OPENAPI_MCP_HEADERS":"<your OPENAPI_MCP_HEADERS>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"anytype": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add anytype --env 'OPENAPI_MCP_HEADERS=<your OPENAPI_MCP_HEADERS>' -- npx -y @anyproto/anytype-mcpOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.anytype]
command = "npx"
args = ["-y", "@anyproto/anytype-mcp"]
env = { OPENAPI_MCP_HEADERS = "<your OPENAPI_MCP_HEADERS>" }If the file already exists, append the block to the end.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"anytype": {
"type": "local",
"command": [
"npx",
"-y",
"@anyproto/anytype-mcp"
],
"environment": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"anytype": {
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "<your OPENAPI_MCP_HEADERS>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OPENAPI_MCP_HEADERSsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Create an API key in the Anytype app settings. Add the anytype server to your MCP client config: command npx, args -y @anyproto/anytype-mcp, and in env set OPENAPI_MCP_HEADERS to a value like {"Authorization":"Bearer key", "Anytype-Version":"date"}.
Other ways from the author
{
"mcpServers": {
"anytype": {
"command": "npx",
"args": ["-y", "@anyproto/anytype-mcp"],
"env": {
"OPENAPI_MCP_HEADERS": "{\"Authorization\":\"Bearer <YOUR_API_KEY>\", \"Anytype-Version\":\"2025-11-08\"}"
}
}
}
}First create an API key in the Anytype app and put it in the Authorization header.
This is third-party code. Review the repository files before installing.
What it does
The server connects an agent to the Anytype app's API and turns its OpenAPI spec into a set of MCP tools. Through chat the agent searches across all spaces or within one, works with spaces and members, objects and lists, properties, tags, types and templates. Successful create, edit and delete return a compact receipt with the object id, and to guard against overwrites it supports an etag precondition and an idempotency key. The server picks the API version at startup: it tries v2 first and falls back to v1 when v2 is absent.
Who it is for. For people who keep a knowledge base or personal wiki in Anytype and want to manage it through an agent.
Good fit when
- You want to search and gather objects in an Anytype knowledge base
- You want to create tasks, notes and lists in natural language
- You want to update object properties, tags and types
Not a fit when
- The Anytype app with its API enabled is not installed
- You cannot trust the client to change and delete objects in the base
Example request
Create a task to study AI trends due in three days and add it to the weekly tasks listLimitations
You need the installed Anytype app and an API key created in the app settings. The key is passed via the OPENAPI_MCP_HEADERS variable in the Authorization header together with the API version. By default the server talks to the app's local address; for anytype-cli or another address set ANYTYPE_API_BASE_URL. API key and pairing management and streaming tools are excluded from the set. The npx launch requires Node.js.
How to disable. Remove the anytype block from your MCP client config and restart it, and optionally revoke the API key in the Anytype app settings.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| OPENAPI_MCP_HEADERS required, secret | JSON with the Authorization header, a Bearer API key and the Anytype version |
| ANYTYPE_API_BASE_URL | API base URL for anytype-cli or a custom port |
Security check
- Creates, changes and deletes objects in your Anytype knowledge base
- Handles an API key passed in the Authorization header
README in short
The README covers getting an API key in the Anytype app and configuring Claude Desktop, Cursor, Windsurf and Claude Code via npx with the OPENAPI_MCP_HEADERS variable. Capabilities span cross-space search, objects and lists, properties and tags, types and templates. It details tool behavior: choosing API version v2 or v1, compact write receipts, the etag precondition and idempotency key, and the exclusion of key management and streaming tools. It also shows setting a custom API base URL and building from source with Bun. The project is developed by Any, MIT licensed.
FAQ
Where do I get an API key?
In the Anytype app under the API Keys settings via the create new key button. There is also a command-line option to fetch a key.
How is the API version chosen?
At startup the server tries the v2 spec first and falls back to v1 when it is absent. You can pin a specific version with an explicit spec URL.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI