Back to blog
Product

The Speakeasy Platform MCP: run the platform from your favorite agent

Nolan Sullivan

Nolan Sullivan

August 28, 2026 · 4 min read

The Speakeasy Platform MCP: run the platform from your favorite agent

Today we're releasing the Speakeasy Platform MCP, so you can govern and secure your company's agents from inside the agent you already work in.

Why go headless?

Agents are becoming the daily driver for enterprise work. A tool that lives only in a web app pulls you out of that work, and its data stays out of reach of anything you build.

Sam Broner put it well:

Sam Broner avatar
Sam Broner@SamBroner

The fact that SaaS co's are giving us agents instead of MCPs shows just how self-centered / narcissistic they are.

I never wanted to "live in your product." Your product was the best way to get something done. If the best way to get it done is now headless, please let me do that.

August 24, 2026

Speakeasy is no different. Our users want to run the platform from their agent, so that's where we put it.

What can the Platform MCP do?

This first release covers the MCP gateway, and the rest of the platform follows. The tools that ship today:

Platform MCP tools

Org and project context

The org you authorized, the projects you can see, and what each one already has.

  • get_platform_context
  • list_projects
  • get_project_overview
  • get_setup_handoff

Finding and adding MCP servers

Search the reviewed catalog, inspect a server before you commit to it, and register it privately into a project. Arbitrary remote MCP URLs register the same way.

  • search_mcp_catalog
  • inspect_mcp_candidate
  • register_catalog_mcp
  • register_remote_mcp

Managing what's in a project

Look up the servers a project already has, edit their metadata, and turn them on or off.

  • find_mcp
  • get_mcp
  • update_mcp_metadata
  • enable_mcp
  • disable_mcp

OAuth and readiness

Connect a server to its OAuth provider, then check whether it works, for the project and for each person.

  • attach_platform_mcp_identity_provider
  • get_mcp_readiness
  • get_user_mcp_status

Troubleshooting

Say whether a failure is us, the provider, or the client, and what to do about it.

  • get_mcp_diagnostics
  • get_mcp_repair_plan

Access control

Which client apps are allowed to call a server.

  • get_mcp_client_admission
  • set_mcp_client_admission

Plugins

The bundle you publish to people. Put a server or a skill on an existing plugin, or take it back off.

  • list_plugins
  • get_plugin
  • distribute_mcp_to_plugin
  • remove_mcp_from_plugin
  • distribute_skill

Skills

Author the skills that ship next to a connection, and version them.

  • list_skills
  • get_skill
  • create_skill
  • update_skill_metadata
  • add_skill_version
  • list_skill_versions

Observability

Events, metrics, and traces for the servers in a project.

  • query_mcp_events
  • query_mcp_metrics
  • query_mcp_traces

Docs and feedback

Search the docs, and send feedback on the MCP itself.

  • search_gram_docs
  • send_platform_mcp_feedback

Get started

The install runs from the dashboard, and the connection is authorized once for the whole organization:

You need an org admin grant on an eligible organization. Ask your Speakeasy contact to turn the Platform MCP on, then open its entry point in the dashboard, install the agent plugin or the documented native config, and authorize the connection.

Need this enabled for your organization? Book time with our team.

Frequently asked questions
What does the Speakeasy Platform MCP include?

The platform admin API as a first-party MCP server, plus reviewed skills. Every tool rechecks a live org admin grant. From Claude, Cursor, or Codex, an org admin can discover a catalog server, register it privately into a project, distribute it onto an existing plugin, and diagnose whether a failure is configuration, the provider, or the client.

How do I get the Speakeasy Platform MCP?

It is a gated rollout to eligible organizations, and it needs an org admin grant and a Speakeasy contact to enable. After that, install the agent plugin for Claude Code, Claude Cowork, or Cursor, or use the documented native config for Codex and OpenCode, then authorize the connection for your organization.

Can the agent attach an identity provider or create plugins?

No. OAuth consent, secret entry, Client ID Metadata Document setup, and remote identity-provider attachment stay human steps in the dashboard. This release also doesn't create, rename, or delete plugins, create organizations or projects, mutate employees or devices, or author a new MCP server from an API. Destructive deletes are out of scope.

Last updated on

AI everywhere.

Control here.