mcp-connections

Add a single object to app/core/catalog/mcp_servers.json with no code changes required. Alternatively, use the Custom server entry, which introspects any reachable MCP server URL without a catalog entry.

Each server gets a 3-second tools/list probe before the turn, and a dead server is skipped with a warning rather than raising an error. Use the /test route and last_status to check whether the connection probe succeeded.

Personal connections are sealed to a member and reached through a binding to each person's own account, while organization connections are sealed to the organization, gated by mcp:manage, and can be named directly in an agent spec.

HubSpot has no dynamic client registration endpoint, so the flow refuses at step two. The fix is registering a client manually at the provider and passing client_id and client_secret to McpOAuthStart.

No. approval_required_tools iterates spec.capabilities only, and MCP tools are discovered at run time, so nothing declares or approves them. Only model tokens count toward budget, not server-side actions.

Tools are prefixed with the connection name, and two connections reducing to the same prefix are deduplicated with the first one winning. Duplicate unprefixed tool names across servers cause Pydantic AI to raise and abort the turn.