Endpoints

One URL per integration.

Hand the same MCP URL to your CI bot, your support agent, and your dev team and you've lost the audit trail before you started. One leaked credential takes out everything.

Endpoints fix that. Each one is its own URL and bearer token, scoped to specific servers, with its own expiration and audit trail. Rotate one without touching the others.

/mcp/ci-pipeline
Active
Server access
GitHub Linear
Expires30 days
Last used2 min ago
Calls1,204
/mcp/support-bot
Active
Server access
Slack Notion Jira
ExpiresNever
Last used8 min ago
Calls12,847
/mcp/dev-readonly
Active
Server access
All servers
Expires7 days
Last used1 hr ago
Calls389

Least-privilege access, out of the box

A URL per integration

Each endpoint gets its own slug like /mcp/ci-pipeline. Audit logs attribute every call to the right endpoint, so you know exactly which integration broke.

Server scoping

Each endpoint can access all servers or only specific ones. Your CI endpoint sees GitHub. Your support endpoint sees Slack and Jira. Nothing else.

Independent revocation

Rotate or delete one endpoint without touching the others. Bearer tokens are hashed with SHA-256 at rest and shown exactly once at creation.

Simple Integration

One URL, one header

Create an endpoint, copy the URL and bearer token into your client config, and you're connected. Every call through that endpoint is logged in the audit trail with the endpoint name attached.

mcp-config.json
{
  "mcpServers": {
    "warpgate": {
      "url": "https://app.usewarpgate.com/mcp/ci-pipeline",
      "headers": {
        "Authorization": "Bearer mcp_xxxxxxxx..."
      }
    }
  }
}

Ship your MCP gateway today

Connect your first server in under five minutes. No credit card required.