Claude Web & Cowork
Add SealGate to claude.ai, Claude Desktop, and Cowork as a custom remote MCP connector.
Cloud Claude clients - claude.ai (the web chat), Claude Desktop, and Cowork - connect to SealGate as a custom remote MCP connector. Unlike local agents such as Claude Code or Cursor, which the desktop client configures automatically, these clients run in Anthropic's cloud, so you add SealGate to them by hand once.
When you add a custom connector, Claude connects to your MCP server from Anthropic's cloud, not from your laptop. Your connection URL must therefore point at SealGate's public gateway (https://mcp.sealgate.ai/...) - a localhost URL from the desktop app's local injection will not work for these clients.
1. Get Your SealGate Connection URL
Your personal connection URL embeds your API key. For Claude, append ?client=claude so SealGate tags the session as Claude in the dashboard:
https://mcp.sealgate.ai/mcp/<your-api-key>/?client=claudeThe easiest way to get this URL is from the SealGate dashboard: open Settings, find the Api key / MCP URL section, click Get MCP URL, and pick Claude from the list - the dialog gives you a ready-to-copy URL with the ?client=claude tag already appended. (Alternatively, copy the base URL from the SealGate desktop app's Copy MCP URL menu and add ?client=claude yourself.) Treat this URL like a password - anyone with it can call MCP tools as you (subject to your Access Control Levels and policies).
The host differs per environment - release is mcp.sealgate.ai, and demo/self-hosted deployments use their own gateway host. Always copy the URL from your own desktop app rather than hardcoding the host.
2. Add the Custom Connector in Claude
How you add the connector depends on whether you're setting it up just for yourself or rolling SealGate out across a team. The connector list lives under Customize > Connectors in every cloud Claude client.
Add SealGate as your own connector. This works on every plan - Free, Pro, Max, and individual Team or Enterprise seats:
- Go to Customize > Connectors.
- Click the + at the top of the connector list and choose Add custom connector.
- Enter a Name (e.g.
SealGate) and paste your connection URL from step 1, including the?client=claudesuffix. - Leave the Advanced settings (OAuth Client ID / Secret) empty - SealGate authenticates via the API key in your URL, not OAuth.
- Click Add.
Free users are limited to a single custom connector.
Do not add one shared SealGate connector for the whole organization. Every SealGate connection URL embeds a personal, per-user API key, and the gateway has no OAuth sign-in. A single org-wide connector would authenticate and attribute every member's activity to the one account whose key is in the URL - collapsing per-user monitoring, attribution, and policy enforcement into a single identity.
To roll SealGate out to a team, have each member add their own personal connector:
- If your workspace restricts custom connectors, an admin first enables them under Admin settings > Connectors.
- Distribute the SealGate desktop app so each member can copy their own connection URL (step 1).
- Each member then follows the Personal steps above with their own URL.
This keeps every member's traffic correctly attributed to them in the SealGate dashboard, where admins get org-wide visibility across all of them.
3. Enable SealGate in a Conversation
In any chat, click the + button, open Connectors, and toggle SealGate on. Claude now routes its tool calls for that conversation through the SealGate gateway, where every call is monitored and policy-enforced.
Claude shows an "unverified service" warning for any custom connector. That is expected for self-added connectors - SealGate still enforces your organization's Access Control Levels and policy rules on every call.