-
Notifications
You must be signed in to change notification settings - Fork 7.7k
add MCP Gateway #22935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
add MCP Gateway #22935
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
d82f725
to
5b8aeb3
Compare
5b8aeb3
to
9e33ba7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ArthurFlag left some comments
@dgageot could you have a look at my comments - I think devils in the details on this one
696fe54
to
2a48c28
Compare
The left nav auto-generates a dropdown if using a folder, even with only a single topic in it. Suggest remove the folder (mcp-gateway), rename the index.md to the folder name (mcp-gateway.md), and update any relative links. I think everything should generate the same except the dropdown. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Picky style guide nits, rest looks great
By unifying multiple MCP servers into a single, secure endpoint, the MCP Gateway offers | ||
the following benefits: | ||
|
||
- Secure by Default: MCP servers run in isolated Docker containers with restricted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Secure by Default: MCP servers run in isolated Docker containers with restricted | |
- Secure by default: MCP servers run in isolated Docker containers with restricted |
|
||
- Secure by Default: MCP servers run in isolated Docker containers with restricted | ||
privileges, network access, and resource usage. | ||
- Unified Management: One gateway endpoint centralizes configuration, credentials, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Unified Management: One gateway endpoint centralizes configuration, credentials, | |
- Unified management: One gateway endpoint centralizes configuration, credentials, |
privileges, network access, and resource usage. | ||
- Unified Management: One gateway endpoint centralizes configuration, credentials, | ||
and access control for all MCP servers. | ||
- Enterprise Observability: Built-in monitoring, logging, and filtering tools ensure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Enterprise Observability: Built-in monitoring, logging, and filtering tools ensure | |
- Enterprise observability: Built-in monitoring, logging, and filtering tools ensure |
|
||
- Developers: Deploy MCP servers locally and in production using Docker Compose, | ||
with built-in support for protocol handling, credential management, and security policies. | ||
- Security Teams: Achieve enterprise-grade isolation and visibility into AI tool |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Security Teams: Achieve enterprise-grade isolation and visibility into AI tool | |
- Security teams: Achieve enterprise-grade isolation and visibility into AI tool |
|
||
## Key features | ||
|
||
- Server Management: List, inspect, and call MCP tools, resoures and prompts from multiple servers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Server Management: List, inspect, and call MCP tools, resoures and prompts from multiple servers | |
- Server management: List, inspect, and call MCP tools, resources and prompts from multiple servers |
|
||
- Server Management: List, inspect, and call MCP tools, resoures and prompts from multiple servers | ||
- Container-based Servers: Run MCP servers as Docker containers with proper isolation | ||
- Secrets Management: Secure handling of API keys and credentials via Docker Desktop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Secrets Management: Secure handling of API keys and credentials via Docker Desktop | |
- Secrets management: Secure handling of API keys and credentials via Docker Desktop |
- Server Management: List, inspect, and call MCP tools, resoures and prompts from multiple servers | ||
- Container-based Servers: Run MCP servers as Docker containers with proper isolation | ||
- Secrets Management: Secure handling of API keys and credentials via Docker Desktop | ||
- Server Catalog: Manage and configure multiple MCP catalogs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Server Catalog: Manage and configure multiple MCP catalogs | |
- Server catalog: Manage and configure multiple MCP catalogs |
- Container-based Servers: Run MCP servers as Docker containers with proper isolation | ||
- Secrets Management: Secure handling of API keys and credentials via Docker Desktop | ||
- Server Catalog: Manage and configure multiple MCP catalogs | ||
- Dynamic Discovery and Reloading: Automatic tool, prompt, and resource discovery from running servers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Dynamic Discovery and Reloading: Automatic tool, prompt, and resource discovery from running servers | |
- Dynamic discovery and reloading: Automatic tool, prompt, and resource discovery from running servers |
|
||
> [!IMPORTANT] | ||
> These instructions are mostly suitable for testing purposes. | ||
> We otherwise recommend building from the sources. See the [readme](https://github.com/docker/mcp-gateway?tab=readme-ov-file#installation). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> We otherwise recommend building from the sources. See the [readme](https://github.com/docker/mcp-gateway?tab=readme-ov-file#installation). | |
> We otherwise recommend building from the sources. See the [README](https://github.com/docker/mcp-gateway?tab=readme-ov-file#installation). |
| macOS | `docker-mcp` | `$HOME/.docker/cli-plugins` | | ||
| Windows | `docker-mcp.exe` | `%USERPROFILE%\.docker\cli-plugins` | | ||
|
||
Or copy it into one of these folders for installing it system-wide. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or copy it into one of these folders for installing it system-wide. | |
Or copy it into one of these folders for installing it system-wide: |
Description
Related issues or tickets
Reviews