Anytype (self-hosted HTTP) MCP Server

Anytype (self-hosted HTTP) is an MCP integration. Self-hosted Anytype MCP server: the full Anytype API as an always-on Docker + HTTP endpoint.

Packages and local setup

The published oci package is ghcr.io/ohneben/anytype-mcp:1.0.6. Its declared MCP transport is streamable-http.

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

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.0.6 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.