For the complete documentation index, see llms.txt. This page is also available as Markdown.

What the Seal MCP server is

The Seal MCP server, Seal's Model Context Protocol endpoint for AI clients.

The Seal MCP server is a Model Context Protocol (MCP) endpoint hosted by Seal. MCP is an open protocol for connecting AI clients to tool servers.

Any MCP-aware client (an IDE assistant, an in-house agent, a Claude Desktop client, and so on) can connect to the endpoint and get tools spanning the same areas as the Seal UI: list discovered packages, create and delete Sealing Rules, trigger Generate fix, query the Dashboard, generate reports, and integrate with GitHub. You also get search over the Seal documentation on the same endpoint, so no second server is needed for that. Every call is scoped to the calling user's tenant.

When to use MCP versus the Public API

For AI-mediated calls, use the MCP server. For non-AI, one-off, or batch integrations, the Public API is the simpler fit.

What it is not

Not a separate permissions model. MCP tool calls use the calling user's role, the same one the Seal UI honors.

Last updated