Run AnythingMCP on your own infrastructure.
AnythingMCP is open source on GitHub. Self-host the whole stack — gateway, dashboard, marketplace, MCP server — for free on Docker, Helm, Railway or DigitalOcean. Credentials stay in your Postgres, every tool call lives in your audit log, your data never reaches our servers.
AGPL-3.0 — free to self-host · every connector included · yours forever
From git clone to MCP endpoint in under 5 minutes.
One script. It bootstraps Docker Compose, generates secrets, sets up the Postgres database and starts every service. No knobs to tune unless you want to.
# Clone the repo
git clone https://github.com/HelpCode-ai/anythingmcp.git
cd anythingmcp
# Run the interactive setup
bash setup.sh
# Ready in ~2 minutes
→ http://localhost:3000 # Visual dashboard
→ http://localhost:4000/mcp # MCP endpointEverything in the Cloud edition — running on your boxes.
The same gateway, dashboard, marketplace and audit log we run in production. Open source so you can read, fork and patch every line.
Every pre-built connector
Every adapter we ship to Cloud is in the OSS repo — SAP, weclapp, DATEV, DHL, Stripe, Magento and the rest. One JSON file each, easy to fork.
Runs anywhere Docker runs
Linux, Mac, Windows via Docker Desktop. Single docker-compose file. Production deploys: Helm chart on K8s, Railway template, DigitalOcean Marketplace.
AES-256-GCM credentials
Every API key and OAuth refresh token is encrypted at rest in your Postgres with AES-256-GCM. Only your own gateway can decrypt them.
Full audit log
Every MCP tool invocation is logged: who, what, when, with which arguments, with the response. Lives in your DB — query it with SQL.
Read every line
Open source under AGPL-3.0. Fork, read, patch, audit. The dashboard, backend and connectors are all in the same monorepo on GitHub.
Active community
GitHub issues and discussions get a maintainer reply within 24 hours on weekdays. New connectors merged weekly. Open RFCs welcome.
Four production-ready paths.
Pick the closest to your stack — they all give you the same dashboard, the same MCP endpoint, the same governance.
Docker Compose
git clone, docker compose up. The default path — works on every dev machine and most VPS hosts. Includes Postgres + Redis + the dashboard.
View setupHelm chart for Kubernetes
Production-grade chart with values for replicas, resource limits, ingress, TLS and an HPA. Ships with the repo under /helm.
Read the chart
Railway one-click
Click, sign in, name your service. Railway provisions Postgres and Redis automatically and ties the env vars together.
Deploy on Railway
DigitalOcean Marketplace
One-click droplet image. Pick the size, paste an SSH key, the app is ready in ~3 minutes. Lowest-latency EU option (Frankfurt).
Deploy on DigitalOceanProtocol reference
Every protocol we wrap into MCP tools.
Each card below links to the technical guide. AnythingMCP turns these protocol shapes into MCP tools automatically — no custom code per system.
Connect anything that speaks a protocol
One connector for every family of systems. From modern REST to legacy SOAP, from databases to MCP-to-MCP chains.
API reference
Hit the gateway directly.
The MCP server is exposed via both REST and GraphQL. Same auth, same tools, same result. Pick whichever your stack already speaks.
curl -X POST \
https://your-gateway/api/mcp/tools/call \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '
"tool": "weclapp_list_invoices",
"args": { "status": "OPEN", "limit": 25 }
'query ListInvoices {
connector(slug: "weclapp") {
call(
tool: "list_invoices"
args: { status: "OPEN" }
) {
result
}
}
}If you can't audit it, you can't trust it.
MCP gateways sit between your AI assistants and your business data. That's a place where the wrong vendor lock-in can cost years. We believe the whole stack — gateway, marketplace adapters, dashboard — should be readable, forkable and runnable without us.
AnythingMCP is open source under the AGPL-3.0 — free to use, modify and self-host for anyone. The one condition: if you modify it and offer it to others as a service, you share those changes. Rather not run it yourself → AnythingMCP Cloud (see /pricing).
How to contribute
- Open an issue for any feature you'd like to see — we triage within a business day.
- Add a connector: copy an adapter JSON, swap endpoint + auth, open a PR. Parametrized tests run automatically.
- Improve a guide on /guides — every guide is an MDX file in /content. Localization PRs welcome.
- RFC: open a Discussion before larger changes to align on shape early.
Same gateway. Different operational story.
Community Edition
Self-hosted, free, open source
- Every connector + visual builder
- Up to 3 users, more with Enterprise
- Full audit log, RBAC, per-tool permissions
- AGPL-3.0 — free, commercial use included
- GitHub issues / Discussions support
AnythingMCP Cloud
Managed, EU-hosted, 7-day free trial
- Zero ops — we handle Postgres, backups, scaling
- Frankfurt EU hosting, DPA on every paid plan
- Managed updates + priority support
- Per-tool permissions, custom roles from Team up
- Commercial license for any company size
Community Edition FAQ
- Is it really open source?
- Yes — the entire repo (backend, dashboard, connectors, docs) is on GitHub under github.com/HelpCode-ai/anythingmcp, licensed under the OSI-approved AGPL-3.0. Only the small ee/ directory (Cloud operation and Business edition licensing) is commercially licensed.
- Can I use it for commercial purposes?
- Yes — the AGPL-3.0 has no revenue threshold: run it commercially, internally or inside your product. Community includes up to 3 active users, Enterprise more. The one obligation: if you modify AnythingMCP and offer it to others over a network, you must share your modified source. For a copyleft-free commercial license, see /pricing.
- What dependencies do I need on my server?
- Docker + Docker Compose, period. Everything else (Postgres, Redis, the dashboard, the MCP server) runs in containers we orchestrate for you.
- Will the open-source version always have the same features as Cloud?
- Yes. The gateway, dashboard, marketplace, audit log and roles are the same code in both. Cloud adds the operations you would otherwise run yourself (managed Postgres, backups, regional pinning, dedicated cloud). Single sign-on and SCIM go the other way: they are available when you self-host, with the Enterprise edition, and not on Cloud.
- How do I get support if something breaks?
- GitHub Issues for bug reports (we reply within 24h on weekdays), Discussions for usage questions. Paid Cloud plans get email/priority support on top.
- How are new connectors added?
- Two paths: open an issue (we ship ~one new connector per week), or contribute one yourself — most adapters are a single JSON file with the API spec + auth profile.
Star us on GitHub — that's how new contributors find us.
Every star moves AnythingMCP higher on GitHub's MCP topic. It's the lowest-effort way to support the project.
AGPL-3.0 — free to self-host · every connector included · yours forever