mcp-gway

One MCP endpoint for every server your agent needs — Code Mode discovers schemas on demand.

Packages

Package details

extensionskill

Install mcp-gway from npm and Pi will load the resources declared by the package manifest.

npm repo home report

$ pi install npm:mcp-gway

Package: mcp-gway
Version: 4.7.1
Published: Oct 12, 2026
Downloads: 749/mo · 749/wk
Author: deuri-vasquez
License: MIT
Types: extension, skill
Size: 63.6 KB
Dependencies: 3 dependencies · 0 peers

Pi manifest JSON

{
  "skills": [
    "./skills/"
  ],
  "extensions": [
    "./.pi/extensions/"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

MCP Gateway

One endpoint for every MCP server your agent needs — fetch tool schemas on demand instead of loading everything upfront.

MCP Gateway aggregates multiple MCP servers behind a single headless HTTP/SSE endpoint. Its Code Mode exposes four meta-tools (listToolFiles, readToolFile, getToolDocs, executeToolCode) so agents discover signatures lazily and execute them in a hermetic Starlark sandbox.

CLI: mcp-gway (canonical) or mgw (alias)
Admin UI: mcp-gway serve --transport http → http://127.0.0.1:8080/

Why MCP Gateway

Fewer wasted tokens — Agents fetch only the schemas they need, when they need them.
One connection to manage — Add, remove, or refresh servers in a single registry; agents connect to one endpoint.
Safe local-first defaults — Binds to 127.0.0.1 by default, screens local commands via an allowlist, masks secrets, and CSRF-protects the admin dashboard.

Who It's For

Agent developers wiring Pi, Antigravity, Claude Desktop, Cursor, or any MCP-compatible client to multiple MCP servers through one gateway.
Operators running local-first infrastructure who want a CLI and dashboard with health probes, Prometheus metrics, and structured JSON logs.

Quick Start

Install: pip install mcp-gway
Add a server: mcp-gway add files --type local --command "npx -y @modelcontextprotocol/server-filesystem /path/to/dir"
List servers: mcp-gway list
Serve HTTP: mcp-gway serve --transport http
Connect: Point your agent to http://127.0.0.1:8080/mcp

For more examples and transports, see the CLI Reference and Integrations.

Features

Multi-Server Aggregation — Connect to multiple MCP servers (local or remote) and expose them through a single endpoint. One URL for every agent; one registry to manage.
Code Mode — Four meta-tools let LLMs discover schemas on demand and execute them in a hermetic sandbox, avoiding the need to load all tool definitions upfront.
OAuth 2.0 Support — Built-in OAuth flow with Dynamic Client Registration (RFC 7591) and secure token storage.
Hermetic Sandbox — Starlark-based sandbox for safe, constrained code execution.
MCP Protocol Compliant — Implements the Model Context Protocol over HTTP, SSE, and stdio.
Local-First Security — Local-first design with SSRF guards, command allow-lists, and CSRF protection.
Built-In Observability — Structured JSON logs, Prometheus metrics, and health probes built in.

Documentation

Configuration & Usage — add servers, transports, and OAuth
CLI Reference — commands, options, and the admin dashboard
Code Mode — lazy-discovery meta-tools and the sandbox
Security — local-first controls and command allow-lists
Observability — JSON logs, Prometheus metrics, health probes
Integrations — Claude Desktop, Pi, Antigravity, OpenCode
Architecture — system diagram and transports
Development — tests, lint, and pre-commit

Development

uv sync --all-groups
uv run pytest -v   # 647 tests

See docs/development.md for checks, probes, and pre-commit.

License

MIT