Continue with your agent

Once setup is done, most day-to-day administration can happen from an agent instead of the dashboard. The Platform MCP is a first-party MCP server that exposes the AI Control Plane to an MCP client such as Claude Code, Cursor, or Codex. An admin can ask the agent to find and add MCP servers, bundle them into plugins, decide who receives them, review shadow MCP servers, tune risk policies, and read usage and security data.

The agent acts with the admin’s own permissions. It never accepts or returns credentials, so any step that needs a secret, such as OAuth consent, hands off to the dashboard through a link.

Access requirements

Connecting the Platform MCP requires the org:admin scope, which the default Admin role includes. The Platform MCP is in beta and is enabled per organization. Open the Headless tab in the dashboard to turn on access, or contact Speakeasy if the tab is missing.

Connect the Platform MCP

Install the Speakeasy plugin from the public marketplace. It registers the Platform MCP server and bundles reviewed skills for common admin workflows. In Claude Code, add the marketplace and install the plugin:

/plugin marketplace add https://github.com/speakeasy-api/marketplace
/plugin install speakeasy@speakeasy

Then run /mcp, select Platform MCP, and choose Authenticate. The browser flow asks which organization to connect, and one authorization covers every tool in that organization. The Headless tab shows the connection once the platform sees it.

Keep the plugin up to date

/plugin marketplace add leaves auto-update off, so the plugin stays on the version you installed. To turn it on for yourself, run /plugin, open Marketplaces, select speakeasy, and choose Enable auto-update.

To roll the plugin out to everyone in the organization with auto-update on, add these settings to managed settings. The same settings also work in ~/.claude/settings.json for one user.

{
  "extraKnownMarketplaces": {
    "speakeasy": {
      "source": {
        "source": "git",
        "url": "https://github.com/speakeasy-api/marketplace"
      },
      "autoUpdate": true
    }
  },
  "enabledPlugins": {
    "speakeasy@speakeasy": true
  }
}

Already have a settings.json?

Create the file if it does not exist. Otherwise, add the speakeasy entry inside the existing extraKnownMarketplaces and speakeasy@speakeasy inside the existing enabledPlugins.

Restart Claude Code for the settings to take effect.

Cursor, Codex, OpenCode, and Claude Cowork install the same plugin through their own marketplace flows, and any MCP client that supports streamable HTTP with OAuth can connect to the endpoint directly. See Connect an agent for each client.

What to ask for

Describe the outcome rather than the steps. For example:

Add the Linear MCP server from the catalog to the Support project and put it on the support plugin.

Show me the shadow MCP servers people used this week and which ones need a review.

Which MCP servers had the most failed tool calls in the last seven days, and why?

The agent chooses the tools. Sensitive changes, such as connecting a server to an identity provider or creating a data export, ask for confirmation first. Adding a server does not distribute it. Nobody receives the server until it is on a published plugin.

Learn more

The Platform MCP reference covers the protocol and authorization details, connection lifetimes, the bundled skills, and every tool the server exposes.