Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Anytype (self-hosted HTTP)

by ohnebenversion 1.0.6i★ –iRuns on your computer
Registry nameio.github.ohneben/anytype-mcp

Install

Overview

Description from the maker (original English)

Self-hosted Anytype MCP server: the full Anytype API as an always-on Docker + HTTP endpoint.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: Streamable HTTP
  • Category: Developer tools
  • You need to fill in: ANYTYPE_API_KEY, MCP_SHARED_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: ANYTYPE_API_KEY, PORT, ANYTYPE_API_BASE_URL, ANYTYPE_VERSION, ANYTYPE_API_HOST_HEADER, MCP_SHARED_TOKEN, ANYTYPE_MCP_SLIM_RESPONSES

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "anytype": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ANYTYPE_API_KEY",
        "-e",
        "PORT",
        "-e",
        "ANYTYPE_API_BASE_URL",
        "-e",
        "ANYTYPE_VERSION",
        "-e",
        "ANYTYPE_API_HOST_HEADER",
        "-e",
        "MCP_SHARED_TOKEN",
        "-e",
        "ANYTYPE_MCP_SLIM_RESPONSES",
        "ghcr.io/ohneben/anytype-mcp:1.0.6"
      ],
      "env": {
        "ANYTYPE_API_KEY": "your-value",
        "PORT": "your-value",
        "ANYTYPE_API_BASE_URL": "your-value",
        "ANYTYPE_VERSION": "your-value",
        "ANYTYPE_API_HOST_HEADER": "your-value",
        "MCP_SHARED_TOKEN": "your-value",
        "ANYTYPE_MCP_SLIM_RESPONSES": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add anytype --env ANYTYPE_API_KEY=your-value --env PORT=your-value --env ANYTYPE_API_BASE_URL=your-value --env ANYTYPE_VERSION=your-value --env ANYTYPE_API_HOST_HEADER=your-value --env MCP_SHARED_TOKEN=your-value --env ANYTYPE_MCP_SLIM_RESPONSES=your-value -- docker run -i --rm -e ANYTYPE_API_KEY -e PORT -e ANYTYPE_API_BASE_URL -e ANYTYPE_VERSION -e ANYTYPE_API_HOST_HEADER -e MCP_SHARED_TOKEN -e ANYTYPE_MCP_SLIM_RESPONSES ghcr.io/ohneben/anytype-mcp:1.0.6

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "anytype": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ANYTYPE_API_KEY",
        "-e",
        "PORT",
        "-e",
        "ANYTYPE_API_BASE_URL",
        "-e",
        "ANYTYPE_VERSION",
        "-e",
        "ANYTYPE_API_HOST_HEADER",
        "-e",
        "MCP_SHARED_TOKEN",
        "-e",
        "ANYTYPE_MCP_SLIM_RESPONSES",
        "ghcr.io/ohneben/anytype-mcp:1.0.6"
      ],
      "env": {
        "ANYTYPE_API_KEY": "your-value",
        "PORT": "your-value",
        "ANYTYPE_API_BASE_URL": "your-value",
        "ANYTYPE_VERSION": "your-value",
        "ANYTYPE_API_HOST_HEADER": "your-value",
        "MCP_SHARED_TOKEN": "your-value",
        "ANYTYPE_MCP_SLIM_RESPONSES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "anytype": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ANYTYPE_API_KEY",
        "-e",
        "PORT",
        "-e",
        "ANYTYPE_API_BASE_URL",
        "-e",
        "ANYTYPE_VERSION",
        "-e",
        "ANYTYPE_API_HOST_HEADER",
        "-e",
        "MCP_SHARED_TOKEN",
        "-e",
        "ANYTYPE_MCP_SLIM_RESPONSES",
        "ghcr.io/ohneben/anytype-mcp:1.0.6"
      ],
      "env": {
        "ANYTYPE_API_KEY": "your-value",
        "PORT": "your-value",
        "ANYTYPE_API_BASE_URL": "your-value",
        "ANYTYPE_VERSION": "your-value",
        "ANYTYPE_API_HOST_HEADER": "your-value",
        "MCP_SHARED_TOKEN": "your-value",
        "ANYTYPE_MCP_SLIM_RESPONSES": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • ANYTYPE_API_KEY secret required env
    Anytype API key, created in the desktop app under Settings -> API Keys.
  • PORT env
    Port the MCP endpoint listens on, inside the container and on the host.
  • ANYTYPE_API_BASE_URL env
    Where the Anytype desktop API is reachable from inside the container.
  • ANYTYPE_VERSION env
    Anytype API version header sent with every request.
  • ANYTYPE_API_HOST_HEADER env
    Override the Host header sent to the Anytype API. Auto-derived when unset; Anytype rejects non-loopback hosts with 403.
  • MCP_SHARED_TOKEN secret env
    Optional bearer token required on the /mcp endpoint. Empty means open, for localhost only.
  • ANYTYPE_MCP_SLIM_RESPONSES env
    Compact API responses before returning them to the client. Set to false for raw payloads.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account ohneben, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 1396 servers in this category
  • Published to the registry more recently than 48% of the other 1396 servers in this category
  • Basic checks equal to or better than 100% of the other 1396 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Anytype (self-hosted HTTP) safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ANYTYPE_API_KEY, MCP_SHARED_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.6) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ohneben Anytype MCP

Talk to your Anytype knowledge base in plain language from AI assistants like Claude, Cursor, and any other MCP client.

This is a self-hosted fork of the official anyproto/anytype-mcp that adds a Docker container and a Streamable-HTTP transport, so the server can run quietly in the background and be reached by any MCP client over HTTP. (The original speaks stdio only.)

Why this one?

The official Anytype MCP server is great, but it runs as a stdio subprocess that each client has to launch on demand. This project keeps 100% of its capabilities and adds a production-style deployment: one always-on server, in Docker, that any number of MCP clients can reach over HTTP.

CapabilityThis projectOfficial anyproto/anytype-mcpOther community servers\*
Full Anytype API coverage (dynamic OpenAPI → MCP tools)✅✅✅
stdio transport✅✅✅
Streamable-HTTP transport (native, or via mcp-remote)✅❌❌
Always-on background service✅❌❌
One server → many clients at once✅❌❌
Docker + docker-compose✅❌❌
Health-check endpoint + auto-restart✅❌❌
Optional bearer-token auth on the endpoint✅❌❌
🟢 / 🟡 / 🔴 read-only / write / destructive tool hints✅➖➖
Automated test suite (Vitest)✅✅➖
LicenseMITMITvaries

\*Community servers such as Qwinty/anytype-mcp (JS), wethegreenpeople/anytype-mcp (Python) and anytype-mcp-plus — most are stdio-only and launched via npx. "➖" = not documented / varies. Snapshot from July 2026; check each project for its latest.

In short: if you just want to try Anytype from your AI client, the official server is perfect. If you want it running in the background, always ready, and shared across every MCP client on your machine, use this one.

What you can do

Once it's connected, ask your assistant things like:

  • "Search my Anytype for notes about the Q3 launch."
  • "Create a task 'Write the report', due in 3 days."
  • "Make a new space called 'Travel' and add a packing checklist."

Tools are generated automatically from your running Anytype app and grouped into 🟢 read-only, 🟡 write, and 🔴 delete.

The server is tuned to keep your assistant fast and frugal with tool calls:

  • `API-get-overview` — a synthesized tool that returns all spaces with their types (or, given a space_id, that space's types and property definitions) in a single call, instead of a list-spaces → list-types → list-properties cascade.
  • Slim responses — API payloads are compacted before they reach the assistant: empty property values, object discriminators, and nulls are dropped, and the type embedded in each search/list result is reduced to its identifiers. This typically shrinks list/search responses by well over half, which means less context burned per call and fewer follow-up calls. Set ANYTYPE_MCP_SLIM_RESPONSES=false to get raw API payloads instead.
  • Routing hints — tool descriptions tell the assistant which tool is cheapest for a job (e.g. search instead of paginating lists, and that only get-object returns the full markdown body).

How it works

Claude / Cursor / …  ──MCP──►  this server  ──HTTP──►  Anytype desktop app (local API)

The server only talks to the local API of the Anytype desktop app on your own machine. Your data stays on your computer.

Requirements

  • The Anytype desktop app, installed and running (it serves a local API at 127.0.0.1:31009).
  • Docker (Docker Desktop on macOS/Windows) for the setup below.

Quick start (Docker)

1. Add your API key. Copy the example config and paste in a key:

cp .env.example .env

open .env and set ANYTYPE_API_KEY=... (see "Get an API key" below)

2. Start the server:

docker compose up -d --build

3. Confirm it's running:

curl -s http://localhost:8769/healthz     # → {"status":"ok"}

4. Connect your MCP client. Add an anytype entry under mcpServers, then fully quit and reopen the app. Pick the form that matches your client:

Claude Code (or any client that speaks Streamable-HTTP natively) — connect directly, no helper process:

"anytype": {

"type": "http", "url": "http://localhost:8769/mcp" }

Claude Desktop (its config is stdio-only) needs the mcp-remote bridge. Install it once, then launch it via node rather than npx:

npm i -g mcp-remote
"anytype": {

"command": "/opt/homebrew/bin/node", "args": [ "/opt/homebrew/lib/node_modules/mcp-remote/dist/proxy.js", "http://localhost:8769/mcp", "--allow-http" ] }

Why not `npx -y mcp-remote …`? npx re-resolves the package through the npm

cache on every launch. When a client cold-starts several MCP servers at once they

contend on that cache, and some launchers can wedge *inside npx* for minutes —

which the client reports as a connection timeout. Installing mcp-remote once and

launching it with node removes that step. Use absolute paths (GUI apps don't

inherit your shell PATH, and mcp-remote's own #!/usr/bin/env node shebang

can't find node otherwise). The paths above are Apple-Silicon Homebrew defaults;

adjust with which node and npm root -g if yours differ.

That's it — ask your assistant to search or create something in Anytype.

Get an API key

In the Anytype desktop app: Settings → API Keys → Create new. Copy the key into .env as ANYTYPE_API_KEY=. Your key stays in .env, which git ignores, so it is never committed.

Configuration

Everything is set in .env (copied from .env.example):

VariableDefaultWhat it does
ANYTYPE_API_KEY—Your Anytype API key. Required.
ANYTYPE_VERSION2025-11-08Anytype API version header.
ANYTYPE_API_BASE_URLhttp://host.docker.internal:31009Where the Anytype app's API is reachable from the container.
ANYTYPE_API_HOST_HEADER*(auto)*Host header sent to the Anytype API. Auto-set to localhost: when the base URL uses a container host alias, because Anytype rejects any other Host with 403 request origin is not allowed.
PORT8769Host port for the MCP endpoint.
MCP_SHARED_TOKEN*(empty)*Optional bearer token to protect the endpoint. Empty = open, for localhost only.
ANYTYPE_MCP_SLIM_RESPONSEStrueCompact API responses before sending them to the assistant. Set to false for raw payloads.

After changing .env, reload with docker compose up -d --force-recreate.

For logs, restart, key rotation, and verification commands, see [DOCKER.md](./DOCKER.md).

Run from source (stdio, no Docker)

Prefer the classic stdio mode? Build it locally:

npm install

npm run build

Then register it with your client using a stdio command and your key in OPENAPI_MCP_HEADERS — see the upstream README for the exact stdio configuration.

Security

  • Your API key lives only in .env, which is git-ignored. Never commit real keys.
  • The HTTP endpoint is unauthenticated by default (fine on localhost). To expose it beyond your machine, set MCP_SHARED_TOKEN and send it as a Bearer header or ?token=….

MCP Registry

This server publishes to the official MCP Registry under the name io.github.ohneben/anytype-mcp. To look up the current listing:

curl "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.ohneben/anytype-mcp"

Its listing is described by server.json and is republished automatically on every v*.*.* tag by .github/workflows/publish-mcp.yml, which waits for the matching GHCR image and authenticates with GitHub OIDC (no secret needed). The registry proves the image is ours via the io.modelcontextprotocol.server.name label in the Dockerfile, so the GHCR package must stay Public.

Releasing

The git tag is the version. Pushing v1.2.3 is the whole release: the tag is stamped into package.json before the image is built and into server.json before the listing is published, so the version the server reports to MCP clients, the image tag, and the registry entry cannot disagree. Nothing needs to be bumped by hand first, and the versions committed here are only the defaults used by local builds.

Credits & license

Built on the official Anytype MCP server by Any Association. Licensed under the MIT License.

Ask PopNx