Add an MCP from the catalog

Use this workflow only through the authenticated Speakeasy AI Control Plane (AICP) Platform MCP. It follows the same guarded outcome a user would complete manually in the AICP dashboard: select a reviewed MCP, configure it for an explicit project, finish secure setup, and verify readiness. The package itself grants no organization access.

If the user instead supplies a remote MCP URL outside the reviewed catalogue, use the add-mcp-from-remote-url workflow.

Safety rules

• Never ask the user to paste API keys, passwords, access or refresh tokens, OAuth codes, client secrets, secret headers, or MCP credentials into chat.
• Never ask the user to supply an MCP endpoint. Use the server-owned catalog candidate and registration workflow.
• Show non-secret provider and setup URLs only when a Platform MCP tool returns them.
• Keep the chosen project and catalog candidate explicit. Do not infer either from a previous conversation or silently substitute another target.
• Registration is private and does not distribute or publish the MCP.
• Use send_platform_mcp_feedback only after asking for consent, and never include identifiers, URLs, credentials, payloads, headers, logs, or attachments.

Workflow