Skip to content

feat: add containerized MCP proxy example#159

Open
ResultantDesign wants to merge 1 commit intogoogle-labs-code:mainfrom
ResultantDesign:feat/container-mcp-proxy
Open

feat: add containerized MCP proxy example#159
ResultantDesign wants to merge 1 commit intogoogle-labs-code:mainfrom
ResultantDesign:feat/container-mcp-proxy

Conversation

@ResultantDesign
Copy link
Copy Markdown

Summary

  • Adds examples/container-proxy/ — a Podman/Docker containerized deployment of the Stitch MCP proxy
  • API key injected via container secrets (/run/secrets/), not environment variables
  • Includes Containerfile, proxy script, and MCP client configuration examples (Claude Code, Cursor, VS Code)

Motivation

The existing run-proxy.ts example requires Node.js and npm on the host. This containerized alternative:

  • No host dependencies — Node.js and packages stay inside the container
  • Secret isolation — API key read from /run/secrets/, never exposed in env vars or CLI args
  • Reproducible — Same image, same behavior everywhere
  • Disposable--rm cleans up after each session

Usage

podman build -t stitch-mcp .
printf '%s' "your-key" | podman secret create stitch-api-key -
podman run --rm -i --secret stitch-api-key stitch-mcp

Test plan

  • podman build -t stitch-mcp . succeeds
  • podman run --rm -i --secret stitch-api-key stitch-mcp connects and discovers 12 tools
  • Verified as MCP server in Claude Code via settings.json configuration

Adds a Podman/Docker container example that runs the Stitch MCP proxy
without requiring Node.js on the host. API key is injected via container
secrets (/run/secrets/) instead of environment variables.

Includes configuration examples for Claude Code, Cursor, and VS Code.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@google-cla
Copy link
Copy Markdown

google-cla bot commented Mar 27, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant