Fix MCP Auth
Never re‑authenticate your MCP servers again
Claude silently drops valid OAuth tokens after a few hours, breaking your Todoist, GitHub, and Slack MCP integrations. Warpgate bypasses the problem entirely.
Sound familiar?
You set up an MCP server, authenticate, start working — and a few hours later it silently stops working. Every time.
Tokens silently expire
Claude applies its own internal TTL to OAuth tokens, even when the server says they're valid for years. Your Todoist token is good for a decade — Claude drops it after hours.
Requests sent without auth
After discarding your token, Claude retries MCP requests without the Authorization header. The server rejects them. No prompt to re-authenticate — just silent failure.
Constant re-authentication
Running /mcp every couple of hours to re-authenticate is not a workflow. It's especially painful with scheduled tasks where there's no one around to re-auth.
This is a known issue affecting Claude Code, Claude Desktop, and Claude.ai. It impacts any OAuth provider that doesn't issue refresh tokens — including GitHub, Todoist, Atlassian, and Slack.
The Fix
Bypass the broken OAuth entirely
Warpgate sits between Claude and your MCP servers. Claude authenticates to Warpgate with a stable bearer token — no OAuth, no expiry, no problem. Warpgate handles the upstream connections server-side.
What you get with Warpgate
Stable auth
Bearer token auth between Claude and Warpgate. No OAuth dance, no token expiry, no silent failures.
Session keepalive
Warpgate pings upstream servers every two minutes. Sessions stay warm so your next tool call is instant.
Health monitoring
See which servers are healthy, degraded, or down at a glance. Know before your next prompt fails.
Auto-retry
If an upstream session expires, Warpgate re-initializes it and retries automatically. No user action needed.
Affected Services
Works with any MCP server
The OAuth token issue affects every MCP server that doesn't return refresh tokens. Route them through Warpgate and the problem disappears — regardless of the upstream auth mechanism.
Warpgate supports HTTP, stdio, and tunnel transports. You can connect cloud-hosted servers, local processes, and even servers behind firewalls via Warpgate Relay.
Todoist
10-year token, still dropped
GitHub
Immortal token, no expires_in
Atlassian
Jira & Confluence MCP
Slack
Workspace integrations
Any OAuth MCP
No refresh token? It's affected
Setup
Up and running in minutes
Add your MCP servers
Point Warpgate at your upstream MCP servers — Todoist, GitHub, Slack, or anything else. Warpgate discovers their tools automatically.
Create an endpoint
Create an endpoint that bundles one or more servers behind a single URL. Warpgate generates a bearer token for authentication.
Point Claude at Warpgate
Replace your direct MCP server configs with one Warpgate URL. Claude authenticates with a bearer token that never expires.
{
"mcpServers": {
"warpgate": {
"type": "streamable-http",
"url": "https://app.usewarpgate.com/mcp/my-endpoint",
"headers": {
"Authorization": "Bearer wg_..."
}
}
}
}One endpoint. All your MCP servers. No OAuth tokens to manage.
Common questions
Why not just wait for Anthropic to fix this?
The issue has been open since February 2025 and affects Claude Code, Claude Desktop, and Claude.ai. Even when fixed, you'll still benefit from centralized config, health monitoring, middleware, and audit logging that a gateway provides.
Does Warpgate add latency?
Minimal. Warpgate caches upstream sessions and keeps them alive with periodic pings. Most tool calls route through an already-warm session with just one extra network hop.
What if my upstream MCP server itself requires OAuth?
Warpgate manages the upstream connection server-side. You configure the upstream server's auth credentials once in Warpgate. Claude never touches those tokens, so Claude's broken token lifecycle doesn't apply.
Does this work with Claude Desktop and Claude.ai too?
Yes. Any MCP client that supports streamable HTTP transport can connect to Warpgate. The bearer token auth is standard and doesn't rely on Claude's OAuth implementation.
How do I get started?
Sign up for free, add your MCP servers, create an endpoint, and swap out your Claude config. The whole setup takes a few minutes.
Explore more
More features to discover
Unified Gateway
Route all MCP traffic through a single, managed endpoint. Warpgate discovers tools automatically.
API to MCP
Import an OpenAPI spec and Warpgate maps every operation to MCP tools automatically.
Audit Trail
Full request-level logging with timestamps, tokens, tools, and response metadata.
Endpoints
A unique URL and bearer token per integration. Scope each endpoint to specific servers with its own expiration and audit trail.
OAuth 2.0 + PKCE
Standard OAuth flow for MCP client authentication.
Teams
Collaborate with role-based access control across your organization.
Warpgate Relay
Securely tunnel local or private MCP servers to the cloud without exposing inbound ports.
Middleware Pipeline
Rate limiting, caching, and transforms on any tool call.
Tool Control
Enable or disable individual tools per server.
Metrics & Health
Real-time health monitoring, per-tool latency tracking, and 30-day uptime history for every MCP server.
Ship your MCP gateway today
Connect your first server in under five minutes. No credit card required.