# mcp.run / TurboMCP documentation

Research date: 2026-09-07

Documentation coverage: partial.

Reference index, not a mirror of complete vendor documentation. Retrieved pages do not prove the MCP works.

## What it does

An enterprise self-hosted MCP gateway and management platform - a trusted, admin-curated registry plus RBAC-controlled deployment of MCP servers across a team's own infrastructure (K8s, PaaS, VMs).

## Access and connection

MCP support: official

Access requirements: enterprise-only (mcp.run 301s to turbomcp.ai, which publishes no pricing at all and positions as a self-hosted enterprise MCP gateway with only run-Turbo-MCP contact and book-a-demo as entry points)

Authentication: Integrates with a team's own OIDC-compatible identity provider; handles OAuth and Dynamic Client Registration for the servers it fronts.

Research checked: 2026-09-07

These details come from catalog research. Check vendor sources for current setup instructions; this is not proof of a tested connection.

## Sources

- https://www.mcp.run
- https://turbomcp.ai
- https://github.com/dylibso/mcp.run-servlets

## Retrieved pages

- https://github.com/dylibso/mcp.run-servlets/actions (fetched)
- https://github.com/dylibso/mcp.run-servlets/pulse (fetched)
- https://github.com/dylibso/mcp.run-servlets/issues (fetched)
- https://github.com/dylibso/mcp.run-servlets/forks (fetched)
- https://github.com/dylibso/mcp.run-servlets/tags (fetched)
- https://github.com/dylibso/mcp.run-servlets/activity (fetched)
- https://github.com/dylibso/mcp.run-servlets (fetched)
- https://github.com/dylibso/mcp.run-servlets/pulls (fetched)