Docker MCP Gateway
Docker MCP Gateway
Since v0.39.0
Introduction
The Testcontainers module for the Docker MCP Gateway.
Adding this module to your project dependencies
Please run the following command to add the Docker MCP Gateway module to your Go dependencies:
go get github.com/testcontainers/testcontainers-go/modules/dockermcpgatewayUsage example
Creating a DockerMCPGateway container
ctx := context.Background()
ctr, err := dmcpg.Run(
ctx, "docker/mcp-gateway:latest",
dmcpg.WithTools("curl", []string{"curl"}),
dmcpg.WithTools("duckduckgo", []string{"fetch_content", "search"}),
dmcpg.WithTools("github-official", []string{"add_issue_comment"}),
)
defer func() {
if err := testcontainers.TerminateContainer(ctr); err != nil {
log.Printf("failed to terminate container: %s", err)
}
}()
if err != nil {
log.Printf("failed to start container: %s", err)
return
}Module Reference
Run function
- Since v0.39.0
The DockerMCPGateway module exposes one entrypoint function to create the DockerMCPGateway container, and this function receives three parameters:
func Run(ctx context.Context, img string, opts ...testcontainers.ContainerCustomizer) (*Container, error)context.Context, the Go context.string, the Docker image to use.testcontainers.ContainerCustomizer, a variadic argument for passing options.
Image
Use the second argument in the Run function to set a valid Docker image. In example: Run(context.Background(), "docker/mcp-gateway:latest").
Container Options
When starting the DockerMCPGateway container, you can pass options in a variadic way to configure it.
The following options are exposed by the testcontainers package.
Basic Options
WithExposedPortsSince v0.37.0WithEnvSince v0.29.0WithWaitStrategySince v0.20.0WithAdditionalWaitStrategySince v0.38.0WithWaitStrategyAndDeadlineSince v0.20.0WithAdditionalWaitStrategyAndDeadlineSince v0.38.0WithEntrypointSince v0.37.0WithEntrypointArgsSince v0.37.0WithCmdSince v0.37.0WithCmdArgsSince v0.37.0WithLabelsSince v0.37.0
Lifecycle Options
WithLifecycleHooksSince v0.38.0WithAdditionalLifecycleHooksSince v0.38.0WithStartupCommandSince v0.25.0WithAfterReadyCommandSince v0.28.0
Files & Mounts Options
WithFilesSince v0.37.0WithMountsSince v0.37.0WithTmpfsSince v0.37.0WithImageMountSince v0.37.0
Build Options
WithDockerfileSince v0.37.0
Logging Options
WithLogConsumersSince v0.28.0WithLogConsumerConfigSince v0.38.0WithLoggerSince v0.29.0
Image Options
WithAlwaysPullSince v0.38.0WithImageSubstitutorsSince v0.26.0WithImagePlatformSince v0.38.0
Networking Options
WithNetworkSince v0.27.0WithNetworkByNameSince v0.38.0WithBridgeNetworkSince v0.38.0WithNewNetworkSince v0.27.0
Advanced Options
WithHostPortAccessSince v0.31.0WithConfigModifierSince v0.20.0 · Chainable since mainWithHostConfigModifierSince v0.20.0 · Chainable since mainWithEndpointSettingsModifierSince v0.20.0 · Chainable since mainCustomizeRequestSince v0.20.0WithNameSince v0.38.0WithNoStartSince v0.38.0WithProviderSince v0.39.0
Experimental Options
WithReuseByNameSince v0.37.0
WithTools
- Since v0.39.0
Use the WithTools option to set the tools from a server to be available in the MCP Gateway container. Adding multiple tools for the same server will append to the existing tools for that server, and no duplicate tools will be added for the same server.
dockermcpgateway.WithTools("brave", []string{"brave_local_search", "brave_web_search"})WithSecrets
- Since v0.39.0
Use the WithSecrets option to set the tools from a server to be available in the MCP Gateway container. Empty keys are not allowed, although empty values are allowed for a key.
dockermcpgateway.WithSecret("github_token", "test_value")
dockermcpgateway.WithSecrets(map[string]{
"github_token": "test_value",
"foo": "bar",
})Container Methods
The DockerMCPGateway container exposes the following methods:
Tools
- Since v0.39.0
Returns a map of tools available in the MCP Gateway container, where the key is the server name and the value is a slice of tool names.
tools := ctr.Tools()GatewayEndpoint
- Since v0.39.0
Returns the endpoint of the MCP Gateway container, which is a string containing the host and mapped port for the default MCP Gateway port (8811/tcp).
endpoint := ctr.GatewayEndpoint()Examples
Connecting to the MCP Gateway using an MCP client
This example shows the usage of the MCP Gateway module to connect with an MCP client.
Run the MCP GatewayGet MCP Gateway's endpointConnect with an MCP clientList tools
ctx := context.Background()
ctr, err := dmcpg.Run(
ctx, "docker/mcp-gateway:latest",
dmcpg.WithTools("curl", []string{"curl"}),
dmcpg.WithTools("duckduckgo", []string{"fetch_content", "search"}),
dmcpg.WithTools("github-official", []string{"add_issue_comment"}),
)
defer func() {
if err := testcontainers.TerminateContainer(ctr); err != nil {
log.Printf("failed to terminate container: %s", err)
}
}()
if err != nil {
log.Printf("failed to start container: %s", err)
return
}gatewayEndpoint, err := ctr.GatewayEndpoint(ctx)
if err != nil {
log.Printf("failed to get gateway endpoint: %s", err)
return
}transport := &mcp.SSEClientTransport{
Endpoint: gatewayEndpoint,
}
client := mcp.NewClient(&mcp.Implementation{Name: "mcp-client", Version: "v1.0.0"}, nil)
cs, err := client.Connect(context.Background(), transport, nil)
if err != nil {
log.Printf("Failed to connect to MCP gateway: %v", err)
return
}mcpTools, err := cs.ListTools(context.Background(), &mcp.ListToolsParams{})
if err != nil {
log.Printf("Failed to list tools: %v", err)
return
}评论
登录后参与评论
KnowForge