MonoMCP Gateway

Unified MCP layer for MonoMCP: serves every organization's toolkits as MCP endpoints with per-tool permissions, an async approval queue, and full request/response audit logging.

Endpoints

/{org_slug}/{toolkit_slug}/mcp

• /mono/seo/mcp — public MonoMCP toolkits (org mono)

• /acme/seo/mcp — a company's private toolkit

• /acme/custom-growth-toolkit/mcp — a custom toolkit

• Enterprise custom domains (mcp.acme.com/seo/mcp) map the Host header to an organization (future work; hook in app.py).

Private toolkits return 404 to callers outside the owning organization — they are not discoverable.

Related MCP server: MCPGate

Auth

Authorization: Bearer <token> where the token is either:

• an org-scoped API key (mmcp_…, created via the api's /api/v1/api-keys), or

• a monomcp JWT access token (from /api/v1/auth/login).

Permissions

Each tool call resolves an effective permission — the caller's role-policy override if one exists, else the tool's org-wide default:

• always_allow — executes immediately

• needs_approval — creates a pending approval request; an admin decides via the api/console; re-calling with the same arguments after approval executes. Poll the built-in approval_status tool for progress.

• blocked — rejected

Every call is persisted to audit_request_logs (source=mcp) with full payloads, duration, status, and actor.

Run

cp .env.example .env   # DATABASE_URL + JWT_SECRET must match the api project
uv sync
uv run uvicorn monomcp_gateway.app:app --port 8765

The database schema is owned by the api project (api/alembic); this project only reads/writes existing tables via the mirror models in src/monomcp_gateway/models.py.