Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 5
- 4 4
- 3 5
- 2 1
- 1 0
Trust in production
- Trust it - 53%
- With caveats - 33%
- Wouldn't - 13%
80% would recommend this server
How reviewers scored it
- Setup & docs 3.7
- Auth experience 3.3
- Reliability 4.0
- Maintainer responsiveness 4.3
Why it got a B
Docker's own open-source gateway, which powers the MCP Toolkit in Docker Desktop. It runs each catalog server in a container with only that server's secrets and checks signatures on Docker's mcp/ images by default. It is an aggregator, so every server you enable through it needs its own review. All ten advisories so far, two critical, were fixed in a release before they were published. Network egress is open by default, so add --block-network or per-server allowHosts. Biggest deduction: it launches servers by calling the docker CLI with catalog arguments, and HTTP mode uses one shared bearer token over plain HTTP, so keep it on stdio or localhost.
How to connect
# per the docker/mcp-gateway README
docker mcp client connect claude-code --profile dev-tools --global
Is Docker MCP Gateway (MCP Toolkit) safe?
Is Docker MCP Gateway (MCP Toolkit) safe to use?
Docker MCP Gateway (MCP Toolkit) grades B (solid, with minor gaps). Login is required, but access is coarse: one sign-in or key covers more than your agent needs, so grant the narrowest account you can. It shells out to helper programs or serves HTTP without enforced TLS, so keep it local and isolated.
Does Docker MCP Gateway (MCP Toolkit) have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Docker MCP Gateway (MCP Toolkit) support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
- A Dynatrace Remote MCP ServerDynatrace's hosted MCP server, running inside your Dynatrace SaaS environment, to run and explain DQL, look into problems, vulnerabilities and Kubernetes events, and forecast time series.
- A GitHub MCP ServerOfficial GitHub server for repos, issues, pull requests, Actions, and code security, hosted or local.
- A GitLab MCP ServerGitLab's built-in MCP server for projects, merge requests, work items, code, and CI pipelines, on GitLab.com or your own instance.
Community reviews
Surprisingly polished
Our agents call this dozens of times a day. Updates land regularly, and nothing broke when I upgraded. Happy to run it in production.
Used for Generating boilerplate from existing patterns
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Mixed feelings after two weeks
It does the job, but it took some tweaking. Sign-in flow was painless and I never had to paste a key into a config file. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Being official from Docker counts for a lot when I pitch it to security.
Used for Scripting routine maintenance tasks
- Setup & docs 2/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Exactly what I needed from Docker Gateway ( Toolkit)
Hooked Docker MCP Gateway (MCP Toolkit) into Claude Code and it worked on the first try. Scoped the token to just what the agent needs and it respected that. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Worth it, just do not skip the hardening steps.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Saves me a context switch every hour
Clear tool names, sensible outputs, very few surprises. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Token setup is the fiddliest part, after that it is smooth. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Easy recommendation.
Used for CI failure investigation
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Worth the five minutes to set up
Started with it as an experiment, now it is a fixture. The Docker image made setup trivial and keeps it isolated. I like that access goes through a proper sign-in instead of a long-lived secret on disk. It is in our production agent and I sleep fine.
Used for CI failure investigation
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Security story needs work
Gave it a fair shot over two weeks. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Filed an issue and got a reply within two days. Fine in production if you sandbox it.
Used for Internal developer assistant
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Capable but needs guardrails
Good for experimenting, still deciding about production. Running it in Docker keeps it away from the rest of my machine. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. I would use it in prod, but only with a human approving writes.
Used for Looking up Docker Gateway ( Toolkit) data without leaving the editor
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Earned a permanent spot in my config
Replaced a homegrown script with Docker MCP Gateway (MCP Toolkit) and have not looked back. Scoped the token to just what the agent needs and it respected that. Used a fine-grained token with short expiry and it works fine with that. Good choice if you need Docker Gateway ( Toolkit) in your agent.
Used for Looking up Docker Gateway ( Toolkit) data without leaving the editor
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Solid core, fiddly setup
Mostly reliable, with the odd timeout. You can tell it is actively maintained, the rough edges keep getting fixed. Not something I would put in production yet.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 2/5
- Auth experience 2/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Does the job, docs could be better
Works well enough for what I need. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. The Docker image made setup trivial and keeps it isolated. Keep permissions tight and it is a good tool.
Used for Code review summaries for pull requests
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Our team uses it every day
Installed it on a Friday, it was part of my workflow by Monday. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Running it in Docker keeps it away from the rest of my machine.
Used for Keeping project tickets in sync with code changes
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Good, but read the permissions first
Useful tool, though I would not hand it to a junior unsupervised. Auth is handled properly, and revoking access later was one click. Nice to use something maintained by Docker rather than a random fork. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent.
Used for Debugging sessions in Cursor
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Solid and well behaved
Tried it on a side project first, then rolled it out at work. Used a fine-grained token with short expiry and it works fine with that.
Used for Letting a coding agent open and triage issues
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Does what it says, no drama
Been running this for about a month now. Scoped the token to just what the agent needs and it respected that. Used a fine-grained token with short expiry and it works fine with that. Would recommend without hesitation.
Used for Keeping project tickets in sync with code changes
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Quietly reliable
Set this up for our team after comparing a few options. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Good choice if you need Docker Gateway ( Toolkit) in your agent.
Used for Automating release notes
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.