Mcpgate MCP Server

Mcpgate MCP server exists for a simple reason — assistants are far more useful when they can act on Mcpgate directly instead of describing what you should do. This repository contains the self-hosting distribution for mcpgate: Docker Compose, configuration templates, hooks, and operations docs. Published container images are released via the CI/CD pipeline connected to this repository.

What the assistant can call

Once Mcpgate is connected, these are the calls the assistant has available:

• Anchor — point the gateway at a git repo (audited, diffable, revertable) or paste content inline (zero git). A configurable poll keeps it fresh; an optional
• Operator — only by default** — the map_read / map_write tools and the freshness beacon are hidden from external / viewer roles. The admin viewer is
• Write — Safety Defaults** — destructive actions (delete, archive, dashboard PUTs) require explicit confirmed=true or force=true. Response size caps prevent
• Post — processing** (observability): response capping, cross-service automation, auth error handling
• Method — Use case
• Service — What your agent can do
• Slack — Search messages, read channels, post messages, manage reminders
• Notion — Pages, databases, blocks, comments, file uploads
• Confluence — Spaces, pages, comments, CQL search
• Jira — Create/update issues, transitions, worklogs, sprints, comments
• GitLab — Issues, merge requests, pipelines, deployments, CI/CD variables, code search
• GitHub — Issues, pull requests, releases, code search across repositories

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Mcpgate's toolset — Anchor, Operator, Write and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mcpgate-de; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Mcpgate.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcpgate mcp server does with a few real requests.