IntegrationsOpt-in

Publish an MCP server once, pin it everywhere

Publish a server manifest (transport, command or URL, allowed tools), and it is signed with the workspace key. Agents point at a name and a range like ^1.2 instead of pasting configs, resolve the newest matching version at run time, and the registry reports drift when a running agent is pinned behind. A CLI publishes from any CI.

Opt in: requires the mcp.registry flag

• Semver-versioned manifests with deprecation and drift reporting
• Ed25519 signatures with a public JWKS endpoint for offline verification
• Per-manifest allowed-tool lists enforced at connection time
• Public read routes and a CLI, so any platform can consume the registry
• Remote transports only: stdio MCP servers are refused by the API

1. Git providersGitHub, GitLab, Bitbucket, and Azure DevOps adapters with PR, issue, branch, and CI support.
2. Ticket systemsJira, Linear, and ClickUp adapters for reading, creating, and updating tickets.
3. Ticket boardsConnect several boards per tracker and read them as a single kanban, filtered, searchable, and writable.
4. LLM modelsOpenAI, Anthropic, Azure OpenAI, AWS Bedrock, OpenRouter, and DeepInfra.
5. VaultAES-256-GCM encrypted workspace secrets, never returned in list endpoints.
6. Public APIOpt-inScoped API keys open a standalone surface: start workflows from your own systems, ingest runs, post heartbeats, read metrics, rotate secrets, publish manifests.