Pantheon is introducing the official Pantheon MCP Server, a governed way to let compatible AI agents operate on your Pantheon fleet through the platform API.
The MCP server exposes Pantheon operations as agent tools, read-only by default, with writes only by explicit opt-in. It forwards the user's own Pantheon identity, so an agent can only reach what that user already can.
What's included
- A stateless MCP server that maps Pantheon operations to agent tools, covering workspaces, sites, environments, builds and deploy status, runtime logs, secrets, and upstreams, with no delete capabilities in this beta.
- Authorization stays with Pantheon: the server forwards the user's own token and the platform decides what that token may see and do.
Who it's for
Developers and teams using compatible AI coding agents who want to manage Pantheon sites and environments through agent workflows while keeping control of what agents can change.
How to get started
Connect from a compatible AI client, sign in with your normal Pantheon account through the OAuth flow, and the client stores your token securely. Disconnect from the Pantheon MCP in the client to log out.
For more details, see related documentation.
Availability
All Pantheon customers. For feedback, please sign up for the Pantheon Community Slack here if you don't already have an account and join us in the #beta-mcp-server channel.
