MCP Ambassador Server
Centralized authentication, authorization, and audit for MCP tools. One server governs every downstream MCP your organization uses.
Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
MCP Ambassador Server is the control plane for managing MCP tools across your organization. It proxies, authenticates, authorizes, and audits every tool call between AI clients and downstream MCP servers. Think of it as what LiteLLM does for LLM providers, but for MCP servers.
Prerequisites: Docker Engine 20+, docker compose v2
git clone https://github.com/mcpambassador/server.git
cd server
cp .env.example .env
docker compose up
Open https://localhost:9443 -- the first-run setup wizard will guide you through creating an admin account.
For production deployment, see the Deployment Guide.
Every MCP goes through a four-step lifecycle before users can access its tools:
Create (draft/pending) --> Validate (draft/valid) --> Discover Tools --> Publish (active)
After publishing, users can browse the Marketplace, subscribe their clients to the MCP, and start using the tools through their AI clients.
Note: If an MCP requires per-user credentials (e.g., API keys), the Discover Tools step will prompt for temporary credentials to use during discovery. These are not stored.
Install the MCP Ambassador Client to connect AI tools to this server.
npm install -g @mcpambassador/client
VS Code configuration example:
{
"mcp.servers": {
"mcpambassador": {
"command": "npx",
"args": ["-y", "@mcpambassador/client", "--config", "/path/to/amb-client-config.json"],
"env": {
"MCP_AMBASSADOR_URL": "https://localhost:8443",
"MCP_AMBASSADOR_PRESHARED_KEY": "amb_pk_YOUR_KEY"
}
}
}
}
See @mcpambassador/client for Claude Desktop, OpenCode, and other integrations.
# Prerequisites: Node.js 20+, pnpm 8.15+
pnpm install
pnpm -r build
pnpm -r test
pnpm -r lint
pnpm -r typecheck
pnpm format:check
MCP Ambassador is configured via environment variables. All settings have production-ready defaults. See mcpambassador.ai/docs/configuration for the full reference.
These settings control session management, health monitoring, and internal scheduling. The defaults are tuned for production use with hundreds of concurrent sessions.
The admin/user web portal polls the server for live data. These intervals balance responsiveness with server load.
For client-side settings (heartbeat interval, cache TTL, catalog refresh), see @mcpambassador/client.
We welcome contributions. See CONTRIBUTING.md for guidelines.
Prerequisites: Node.js 20+, pnpm 8.15+, Docker
MCP Ambassador is free and open source. If it's useful to you, consider supporting development.
Support via GitHub Sponsors: https://github.com/sponsors/mcpambassador
Crypto donations:
3QH4WQoQqnhU3LhbZQU8ttXaNco5Ge3xVp0xa5462444c5AEf0B2e32822D9a9B7f91aC794FfF0Apache License 2.0 -- see LICENSE.
MCP Ambassador is at v0.8.0-beta.2. The API may change before 1.0. Production use is supported but expect breaking changes during the beta period.
Open-source MCP governance proxy -- authentication, authorization, audit, and a marketplace for AI tools. Self-hosted via Docker.
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Mcpambassador läuft lokal über stdio.
Zuletzt geprüft: 2026-10-28. Open-source MCP governance proxy -- authentication, authorization, audit, and a marketplace for AI tools. Self-hosted via Docker.