Massdriver

What the Massdriver MCP server does

The Massdriver MCP server exposes Massdriver infrastructure management through the Model Context Protocol. It gives an MCP client tools for inspecting and changing projects, environments, instances, deployments, components, bundles, resources, policies, groups, service accounts, OCI repositories, and organization settings.

The toolset includes read operations such as listing and retrieving objects, along with changes such as creating, updating, deleting, deploying, rolling back, approving, rejecting, and decommissioning. It also includes viewer information, server and URL lookup, audit log access, policy evaluation, deployment comparisons, environment comparisons, and dependency-related queries.

Service account creation is intentionally excluded, so the server cannot mint new credentials.

How it works

The Massdriver MCP server authenticates to a Massdriver organization with an API key and organization ID. Configuration can come from environment variables or a named profile in ~/.config/massdriver/config.yaml. The default transport is MCP over stdio, which suits local integrations. A Streamable HTTP mode is available with the -http flag or MASSDRIVER_MCP_HTTP_ADDR.

The HTTP endpoint is stateless and accepts JSON requests without a session handshake. Because it is unauthenticated while exposing infrastructure-mutating tools, it should be bound to localhost or protected by an authenticating proxy.

Setup and configuration

Install a platform release for Linux, macOS, or Windows, use go install with Go 1.25 or newer, pull the Docker image, or build from source with the repository's Make target. Registry-aware clients can discover the package as cloud.massdriver/mcp-server.

Set MASSDRIVER_API_KEY and MASSDRIVER_ORGANIZATION_ID before starting the process. Set MASSDRIVER_URL for a self-hosted Massdriver instance, and use MASSDRIVER_PROFILE to select a configuration profile. Docker users running stdio must pass interactive stdin with -i; profile-based Docker setups also need the configuration directory mounted and XDG_CONFIG_HOME configured.

Claude Code and Claude Desktop have documented setup examples. The stdio transport is also described as compatible with any MCP client.

Tools and capabilities

The 111 tools are grouped across these areas:

• Projects and environments, including cloning, comparison, deployment, forking, and decommissioning.
• Instances, components, bundles, resources, resource types, and resource grants.
• Deployments, including planning, proposals, approvals, rejection, abortion, rollback, logs, and comparisons.
• Organization data, viewer details, audit logs, groups, memberships, invitations, and service accounts.
• OCI repositories and grants.
• Policies, including creation, evaluation, batch evaluation, explanation, and attribute lookups.

Limitations and notes

An API key and organization ID are required unless credentials are supplied through a configured profile. The HTTP mode has no built-in authentication, so exposing it beyond a trusted boundary can allow access to mutating infrastructure tools. The server does not expose service account creation. Detailed per-tool input conventions, pagination behavior, and annotations are maintained in MCP_README.md in the repository.