MCP Gateway
MCP Gateway is the unified access point for all MCP servers in Archestra Platform. It provides a single endpoint through which AI agents and applications can discover and interact with multiple MCP servers, regardless of whether they are remote services or locally orchestrated containers.
To use MCP Gateway:
- Go to MCP Registry and make sure you have at least one MCP server installed.
- Go to MCP Gateways and create a new gateway or use an existing one.
- Click the pencil icon to open the Edit MCP Gateway form.
- In the Tools section, assign MCP server tools to the MCP Gateway and save the changes by pressing Update.
- Click the Connect icon to get connection instructions.
Authentication
Archestra's MCP Gateways support two authentication methods:
OAuth 2.1 (Recommended for MCP Clients)
The gateway implements the MCP Authorization specification with OAuth 2.1. MCP clients that support OAuth can authenticate automatically — the client discovers endpoints via standard metadata URLs, performs an authorization code flow with PKCE, and receives an access token.
POST /v1/mcp/<profile_id>
Authorization: Bearer <access_token>
Discovery endpoints:
| Endpoint | Purpose |
|---|---|
GET /.well-known/oauth-protected-resource/v1/mcp/<profile_id> | Resource metadata (RFC 9728) |
GET /.well-known/oauth-authorization-server | Authorization server metadata (RFC 8414) |
Bearer Token
For direct API integrations, use Archestra-issued tokens in the Authorization header. Tokens can be scoped to an individual user, a team, or the entire organization — controlling which MCP Gateways and credentials are accessible.
POST /v1/mcp/<profile_id>
Authorization: Bearer archestra_<token>
Create tokens in Settings → Tokens or via the Archestra API.