Add a Trusted STDIO MCP

Local STDIO servers are Git- and image-managed. Organization-created integrations cannot provide a command, package, or environment.

Add the Server

1. Pin the exact package version in apps/agents.

   bun add --cwd apps/agents --exact <package>@<version>

2. Add a stable definition to apps/agents/src/mcp/registry.ts.

3. Define the trusted command, arguments, named environment references, and bounded timeouts.

4. Grant the registry key through commonMcpServerKeys or a profile’s mcpServerKeys.

5. Rebuild the agent image.

6. Publish the catalog and reprovision when static grants change.

Registry Rules

• The registry is the only key-to-executable mapping.
• Unknown keys fail closed.
• Catalog profile kind must not secretly determine entitlement.
• A database row can select a trusted key but never replace its command.
• Do not use runtime npx, bunx, floating downloads, or package installation.

Test

• Exact registry definition.
• Unknown-key rejection.
• Granted and ungranted profiles.
• Startup and tool timeout behavior.
• Environment allowlist.
• Image contains the pinned package.
• Workspace and process cleanup.
• Static MCP and organization integrations merge without key collision.

The built-in structured-questions server is the reference implementation.