Self-hosted MCP gateway
Your AI, connected to every tool your company works with.
Ask once: it reads the Jira ticket, checks the logs in Grafana, and posts the answer to Slack. One secure endpoint for Claude, Codex, ChatGPT and Gemini.
- PII pseudonymized before the model sees it
- Grounded in your company’s context
- 50+ connectors, plus your own APIs
- Every tool call audited, with pseudonymized actors
- Service tokens stay in your gateway: AES-256-GCM, optional Cloud KMS
Free for up to 5 users.
More productivity, less copy & paste
Connect everything with everything.
mcpgate reads Jira and GitLab for you and writes to Slack. Your AI client asks before writing, as you set it up; for risky actions, such as deleting a whole project, mcpgate asks too.
Customer data, masked before the AI sees it
Two layers: the gateway masks what its tools return, for every AI client. maisecrets masks what Claude Code, Cowork and Codex read on your laptop.
maisecrets in Claude Code: you see the value, a click copies it
| From a support ticket | You see | The AI gets |
|---|---|---|
| Name | Laura Becker 🔒 | ⟦NAME_c1⟧ |
| laura.becker@kunde.mcpgate.de 🔒 | ⟦EMAIL_c2:la•••@•••.de⟧ | |
| Password | ⟦SECRET_c3⟧ 🔒 | ⟦SECRET_c3⟧ |
| Masked data | Rules (default) | + name service |
|---|---|---|
| Keys, tokens, passwords | ✓ | ✓ |
| E-mail, IBAN, card, phone (+49 …) | ✓ | ✓ |
| Names after a label or in a column | ✓ | ✓ |
| Names in running text | – | ✓ |
The rules run on every computer, with no model to download. For names in running text, add the name service: on your computer, or once in your mcpgate.
Context is king, not the model
Ever gotten a confident answer that was just wrong? That’s missing context.
An answer sounds just as sure whether it's grounded in your reality or guessing. Without context, the AI parks at high confidence, low quality — that gap is overconfidence.
A shared, curated company map moves answers right; personal context moves it further — quality climbs toward confidence. The gap shrinks; it doesn't vanish, and we don't pretend it does.
Context Map: what exists, and when did it change?
Your AI asks the Context Map for where and who, and stays current.
Your team updates the map by asking its AI, over MCP; every change is versioned in git. A change reaches every open session with its next tool call, without an extra request.
Room for the right context
Fewer tokens per connected tool. Plus per-action audit, PII scrubbing and policy hooks raw MCP doesn’t give you. Drag to model your own stack:
Speaking of the right context — only a lean set of tools stays resident. The rest — thousands of actions across every connected service — stay out of your window, discovered on demand via search when the AI needs them. That’s why each added service costs ~550 tokens here, not 11k.
Automations run through the same door
Windmill, n8n or your own agent: same rights, same rules, same audit.
Every call is audited. Flows built in n8n, Zapier or Make can call the gateway too.
Run it on your own infrastructure
One command. Self-hosted. No .env file needed.
curl -fsSL https://mcpgate.de/install.sh | bash
- Source-available — read what runs
- Self-hosted
- Your prompts are not logged
Reviewable shell script. The gateway runs on your own infrastructure.
View install script · View Docker Compose file · Hardware requirements
- 1Run the command aboveit checks Docker and starts the stack
- 2Open localhost:8642the wizard signs you in
- 3Connect your AI clientClaude, Codex, Gemini or ChatGPT
- 4Set up your servicesin the admin UI, or let your AI do it over MCP
Try the demo Full quickstart →
Demo with sample data: no signup, no credit card.
Read first
All posts →What flows through, what gets blocked, what gets logged
Audit, PII sanitization, throughput as a DLP lens, policy hooks — four layers stacked on the same audit trail. How they fit together, and the data-exfiltration signal you do not want to be missing.
Read →Dynamic action discovery isn’t novel. Doing it safely is.
Anthropic shipped Tool Search in November 2025. mcpproxy-go has BM25. Stacklok benchmarks 94% retrieval. What the gateway market converged on, and what mcpgate chose differently.
Read →mcpgate vs Obot: which self-hosted MCP gateway?
Side-by-side: where Obot is the better choice (maturity, MIT license, Kubernetes day one), where mcpgate is (PII pseudonymization, two-layer policy hooks).
Read →