AnythingMCP MCP server

AnythingMCP

Give Claude, ChatGPT and Copilot safe access to the software your company already runs. 257 ready adapters, any REST/SOAP/GraphQL/SQL system without code, on your own infrastructure — and it learns how your systems connect.

Claude answering a question no chatbot could answer, because the data lives in a field-service system that speaks REST, not MCP:

Run it yourself — three lines, no clone, details below:

mkdir anythingmcp && cd anythingmcp
curl -fsSLo docker-compose.yml \
  https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d   # → http://localhost:3000

Three words appear throughout and mean three different things:

• an adapter is one of the 255 JSON definitions that ship in this repo — DATEV, weclapp, DHL, Deutsche Bahn, Shopware, Personio, Handelsregister and the rest. 20 of them need no API key at all; the others ask for your credentials at import.
• a connector is an adapter, or your own OpenAPI spec / Postman collection / WSDL / GraphQL endpoint / database, once you have configured it in your workspace. Anything you can point at, in minutes, without writing an MCP server.
• an MCP server is the URL you hand to Claude. It exposes the connectors you assign to it, and nothing else.

Everything runs on your infrastructure, so you decide what leaves it. Per-tool response mapping declares which fields ever reach the model; credentials are AES-256-GCM at rest; the audit log keeps the full upstream response on your side. OAuth2, RBAC, SSO and SCIM are in the self-hosted build, not held back for a paid tier.

In production at KOCH Freiburg GmbH, where it connects AI assistants to 15+ internal systems — ERP, CRM, SOAP services and on-prem databases. AnythingMCP was extracted from that system by helpcode.ai in Freiburg, Germany, and open-sourced because an adapter catalog grows faster as a community than as a product.

Run it yourself

The recommended path, and the one measured below. Requires Docker 24+ and openssl; on macOS, start Docker Desktop first.

Shortened. The full README is on GitHub.