Gateway

ai.sealgatePublished by sealgate.aiOfficial publisherv1.0.0Updated Oct 24, 2026

MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

Sealgate's remote MCP gateway that proxies agent tool calls through access-control policies and logs what agents did.

What you can do
  • List the MCP servers governed by your Sealgate gateway, with access-control classification and connection status
  • Review recent agent sessions and audit events: what agents did, which data flowed, and any blocked actions
  • Aggregate every enabled MCP server behind one Streamable HTTP endpoint that enforces Sealgate policies on each call
  • Front Sealgate's messaging connectors so agents can read and send across chat networks under the same policy checks and audit log
When to use it
Use it when an organisation already runs Sealgate and wants AI agents to reach its tools and data through a single governed endpoint with per-call policy enforcement and an audit trail, rather than connecting to each MCP server directly.
Requirements
A remote Streamable HTTP endpoint; no install needed for the hosted gateway. Sign-in is OAuth 2.1 in the browser (dynamic client registration, PKCE, refresh tokens). Clients that cannot run OAuth can pass a Sealgate API key as a URL path segment. The stdio npm alternative needs SEALGATE_GATEWAY_URL and SEALGATE_API_KEY. Team and Enterprise Claude plans require an admin to add it.
Before you install
The API-key-in-URL option puts the key in the path rather than an Authorization header, so it can leak through logs or shared links; prefer OAuth. The gateway mediates access to your organisation's data and tools and to messaging networks, so agents may read and send messages and other data under your identity. Review the access-control policies and audit log before enabling broad tool access.

Installation

In SourceWeft

  1. Open Gateway in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.sealgate%2Fgateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gateway": {
      "type": "http",
      "url": "https://mcp.sealgate.ai/mcp"
    }
  }
}

README

[SealGate — connect & govern how AI interacts with your data]

Sealgate MCP Server

[MCP] [npm] [smithery badge] [MCP Registry] [License: MIT]

The Model Context Protocol (MCP) server for Sealgate, the AI data-leak-prevention platform: a security gateway and data firewall that sits between AI agents (Claude, ChatGPT, Cursor, Copilot) and your organisation's data and tools.

This server is a thin MCP proxy. It forwards a small set of tool calls to a Sealgate gateway, which you configure with two environment variables. Sealgate runs managed release hosts (the remote MCP gateway at mcp.sealgate.ai and the Management API at dashboard.sealgate.ai), and demo or self-hosted orgs run their own, so this bridge stays host-agnostic: you supply the URL and key.

Tools

ToolWhat it does
list_mcp_serversList the MCP servers governed by your Sealgate gateway, with access-control classification and connection status.
get_session_statusReview recent agent sessions and audit events: what agents did, which data flowed, and any blocked actions.

Connect to the hosted gateway

Sealgate runs a managed remote MCP gateway at https://mcp.sealgate.ai/mcp. It is a per-user proxy that aggregates every MCP server you have enabled behind one Streamable HTTP endpoint and enforces Sealgate's access-control policies on every call. There is nothing to install: point your client at the endpoint and sign in through the browser.

text
Endpoint:   https://mcp.sealgate.ai/mcpTransport:  streamable HTTP (remote, not stdio)Auth:       OAuth 2.1 in the browser, no key to paste
ClientAdd it
[Image] ClaudeAdd to Claude opens the Add custom connector dialog with the name and URL filled in. Claude flags it as suggested by an external link; that is expected. On Team and Enterprise plans an admin adds it.
[Image] ChatGPTSettings → Connectors → Advanced settings → turn on Developer mode. Back on Connectors, click Create, paste the endpoint, and name it. Start a new chat so the tools menu refreshes.
[Image] Claude Codeclaude mcp add --transport http --scope user sealgate https://mcp.sealgate.ai/mcp
Then run /mcp in a session to sign in.
[Image] Cursor[Add to Cursor]
Not working? Add the endpoint by hand under Settings → MCP.
[Image] VS CodeAdd to VS Code requires Copilot agent mode.
[Image] Goose[Install in Goose]
Adds it as an extension over streamable HTTP.
[Image] GrokbotAdd a remote MCP server pointing at https://mcp.sealgate.ai/mcp over streamable HTTP, then sign in through the browser.
[Image] Any MCP clientAdd a remote server at https://mcp.sealgate.ai/mcp over streamable HTTP. Cline, Zed and Windsurf all work; each spells the config differently (VS Code servers, Cursor and Cline mcpServers, Zed context_servers, and Windsurf wants serverUrl where everyone else wants url).

Every one-click button routes through an https:// install URL, since GitHub strips custom URL schemes such as cursor:// from links.

How OAuth works

The gateway is an OAuth 2.1 authorization server, so most clients connect with no API key at all. The flow uses dynamic client registration (RFC 7591) and client ID metadata documents, mandatory PKCE (S256), and issues refresh tokens via the offline_access scope, so a session stays connected without re-authenticating every hour. Discovery, consent, and token endpoints all live on the gateway origin, so self-hosted single-origin deployments work with no extra configuration.

API key in the URL

Clients that cannot run an OAuth flow can pass a Sealgate API key as a URL path segment instead:

https://mcp.sealgate.ai/mcp/{api_key}/?client={label}

Replace {api_key} with the key from your dashboard and {label} with an optional session label. This is not OAuth and not an Authorization header; the key travels in the path.

mcp.sealgate.ai is the managed release host. Demo and self-hosted orgs run their own gateway host, so substitute your own URL where needed.

Connect your messaging apps

The same gateway fronts Sealgate's messaging connectors (the Beeper desktop app plus the sealgate-stdiod tunnel), so any client above can read and send across your chat networks. Every message an agent reads or sends passes through the same policy checks and lands in the same audit log as every other tool call.

NetworkGuide
[Image] WhatsApphttps://sealgate.ai/connect/whatsapp
[Image] Telegramhttps://sealgate.ai/connect/telegram
[Image] iMessagehttps://sealgate.ai/connect/imessage
[Image] Signalhttps://sealgate.ai/connect/signal
[Image] LinkedIn DMshttps://sealgate.ai/connect/linkedin
[Image] Instagramhttps://sealgate.ai/connect/instagram
[Image] Messengerhttps://sealgate.ai/connect/messenger
[Image] Discordhttps://sealgate.ai/connect/discord
[Image] Xhttps://sealgate.ai/connect/x
[Image] LINEhttps://sealgate.ai/connect/line
Per-client guidesCodex + iMessage, Claude + LinkedIn, ChatGPT + WhatsApp, and all 100 at https://sealgate.ai/connect

Codex + iMessage in one command: the companion repo Edison-Watch/codex-imessage wires Codex to iMessage through the gateway with a single install step.

Configuration

Set two environment variables, both issued or hosted by your organisation:

VariableDescription
SEALGATE_GATEWAY_URLBase URL of your Sealgate Management API (e.g. https://dashboard.sealgate.ai).
SEALGATE_API_KEYSealgate API key from your dashboard.

If either is unset, every tool returns a clear configuration message instead of failing, so registry probes and --help never crash.

Install

Prefer the hosted gateway above. The npm package is the stdio alternative for clients that cannot use a remote server; it runs via npx and needs the two environment variables from Configuration. Also published in the official MCP Registry as ai.sealgate/gateway and io.github.Edison-Watch/sealgate-mcp.

json
{    "mcpServers": {        "sealgate": {            "command": "npx",            "args": ["-y", "@sealgate/mcp"],            "env": {                "SEALGATE_GATEWAY_URL": "https://dashboard.sealgate.ai",                "SEALGATE_API_KEY": "your-sealgate-api-key"            }        }    }}

VS Code spells the same block as servers with "type": "stdio". Ready-made files for each client live in examples/.

Usage

bash
# Run over stdio (default transport)npx -y @sealgate/mcp
# Show usagenpx -y @sealgate/mcp --help

Set SEALGATE_MCP_TRANSPORT=http (with an optional PORT, default 3000) to serve streamable HTTP instead of stdio.

Develop

Requires Bun.

bash
bun installbun run src/index.ts --help   # run from sourcebun test                      # run testsbun run build                 # bundle to dist/make ci                       # lint, typecheck, dead-code, and the rest

Links

License

MIT. Copyright GPU-EVM LTD (Sealgate). See LICENSE.

Source: README.md at commit 679f868

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Sealgate integrations

Sealgate

Published by GitHub account Edison-Watch

Sealgate's MCP proxy lets an assistant list the MCP servers governed by a Sealgate gateway and review agent session and audit status.

Streamable HTTPWeb executable
Cloud & InfrastructureNot indexed yetOct 24, 2026