add-mcp-from-catalog

Installation
SKILL.md

Add an MCP from the catalog

If this connection lists call_platform_tool instead of the tools this workflow names, find each named tool with search_platform_tools, describe it with describe_platform_tool, then run it with call_platform_tool and the same arguments. Whether a tool exists for you is decided by describe_platform_tool with its exact name, not by tools/list or one page of search results: a name returned in not_found is unavailable to you, so say so rather than guess. The call itself still checks your access. When execute is also listed, a multi-step read may run in execute with tools.search, tools.describe and tools.call on platform--<tool name> paths. End each execute run at a confirmation point and ask the user before any write.

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. The person who added it can use it once it is ready; sharing it through a plugin is optional.
  • Use send_platform_mcp_feedback only after asking for consent, and never include identifiers, URLs, credentials, payloads, headers, logs, or attachments.

Workflow

Installs
2
First Seen
Aug 27, 2026