Massdriver

cloud.massdriverPublished by massdriver.cloudv0.2.0Updated Oct 24, 2026

Manage the Massdriver infrastructure platform: projects, environments, deployments, and more.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Massdriver MCP server lets an AI assistant manage Massdriver infrastructure: projects, environments, deployments, components, policies and organization settings

What you can do
List, create, clone, update and delete projects and environments, including forking, comparing, deploying and decommissioning environments and managing environment links and dependencies. Inspect and change instances, components and resources, including secrets, remote references, links, grants and alarms. Create, plan, propose, approve, reject, abort, roll back and compare deployments, and read deployment logs. Manage organization settings, custom attributes, members, groups, service accounts, OCI repositories and policies, including evaluating and explaining policies. Read audit logs, bundles, resource types, the current viewer and server information.
When to use it
Useful when you want an assistant to inspect or operate a Massdriver infrastructure platform through conversation: reviewing deployments and logs, comparing environments, checking policies or audit events, or making changes to projects, environments and resources without switching to the Massdriver UI.
Requirements
Runs as a local process over stdio, installed from a release binary, Go install, Docker image or source build. Requires a Massdriver API key in MASSDRIVER_API_KEY and an organization ID in MASSDRIVER_ORGANIZATION_ID, supplied as environment variables or via a profile in the Massdriver config file. MASSDRIVER_URL is only needed for self-hosted instances. Network access to the Massdriver API.
Before you install
The server holds a Massdriver API key and can perform infrastructure-mutating actions: creating, updating and deleting projects, environments, resources, groups, policies and OCI repositories, setting and removing instance secrets, and deploying, approving, aborting or rolling back deployments. An optional HTTP transport is unauthenticated and exposes these mutating tools, so bind it to localhost or put it behind an authenticating proxy. Service account creation is deliberately not exposed.

Installation

In SourceWeft

  1. Open Massdriver in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Massdriver MCP Server

A Model Context Protocol (MCP) server for Massdriver, providing AI assistants with tools to manage your infrastructure platform — projects, environments, deployments, policies, and more.

Installation

This server is published to the official MCP Registry as cloud.massdriver/mcp-server — MCP clients with registry support can discover and install it by that name.

To install manually, pick whichever suits your setup:

Download a release binary — grab the archive for your platform (Linux, macOS, or Windows; amd64 and arm64) from GitHub Releases and put mcp-server on your PATH.

Go install (requires Go 1.25+):

bash
go install github.com/massdriver-cloud/mcp-server@latest

Docker:

bash
docker pull massdrivercloud/mcp-server

Build from source:

bash
git clone https://github.com/massdriver-cloud/mcp-server.gitcd mcp-servermake build   # outputs ./bin/mcp-server

Configuration

You'll need a Massdriver API key and your organization ID — see the Massdriver docs for creating API credentials.

The server reads configuration from environment variables, or from a profile in ~/.config/massdriver/config.yaml:

bash
export MASSDRIVER_API_KEY="your-api-key"export MASSDRIVER_ORGANIZATION_ID="your-org-id"# Optional:export MASSDRIVER_URL="https://api.massdriver.cloud"  # set this if you run a self-hosted Massdriver instanceexport MASSDRIVER_PROFILE="default"                   # named profile in ~/.config/massdriver/config.yaml

Transports

By default the server speaks MCP over stdio (for local tool integrations like Claude Desktop). To serve the Streamable HTTP transport instead, pass -http (or set MASSDRIVER_MCP_HTTP_ADDR):

bash
./bin/mcp-server -http 127.0.0.1:8080

The HTTP endpoint is stateless and returns application/json, so a single tool call is a plain POST (no session handshake required):

bash
curl -s 127.0.0.1:8080 \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_viewer","arguments":{}}}'

The HTTP endpoint is unauthenticated and exposes infrastructure-mutating tools. Bind it to localhost or place it behind an authenticating proxy.

Docker

The stdio transport needs an interactive stdin, so pass -i:

bash
docker run --rm -i \  -e MASSDRIVER_API_KEY \  -e MASSDRIVER_ORGANIZATION_ID \  massdrivercloud/mcp-server

On a self-hosted Massdriver instance, also pass -e MASSDRIVER_URL.

Using a profile? MASSDRIVER_PROFILE reads credentials from ~/.config/massdriver/config.yaml, which doesn't exist inside the container. Either pass the credentials as environment variables as shown above, or mount your config directory and point XDG_CONFIG_HOME at it:

bash
docker run --rm -i \  -e MASSDRIVER_PROFILE \  -e XDG_CONFIG_HOME=/config \  -v ~/.config/massdriver:/config/massdriver:ro \  massdrivercloud/mcp-server

MCP Client Configuration

Claude Code

bash
claude mcp add massdriver \  --env MASSDRIVER_API_KEY=your-api-key \  --env MASSDRIVER_ORGANIZATION_ID=your-org-id \  -- /path/to/mcp-server

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "massdriver": {      "command": "/path/to/mcp-server",      "env": {        "MASSDRIVER_API_KEY": "your-api-key",        "MASSDRIVER_ORGANIZATION_ID": "your-org-id"      }    }  }}

Other Clients

The server uses stdio transport, compatible with any MCP client.

Available Tools (111)

See MCP_README.md for the full tool reference, including per-tool descriptions, input conventions, pagination, and behavioral annotations.

Projects (6)

list_projects get_project create_project clone_project update_project delete_project

Environments (13)

list_environments get_environment create_environment update_environment delete_environment set_environment_default remove_environment_default compare_environments fork_environment deploy_environment decommission_environment list_environment_links list_environment_unfulfilled_dependencies

Instances (10)

list_instances get_instance update_instance set_instance_secret remove_instance_secret set_remote_reference remove_remote_reference copy_instance orphan_instance list_alarms

Deployments (11)

list_deployments get_deployment get_deployment_logs create_deployment propose_deployment approve_deployment reject_deployment abort_deployment plan_deployment rollback_deployment compare_deployments

Components (8)

list_components get_component add_component update_component set_component_position remove_component link_components unlink_components

Bundles (1)

get_bundle

Resources (9)

list_resources get_resource create_resource update_resource delete_resource export_resource create_resource_grant delete_resource_grant list_resource_grants

Resource Types (2)

get_resource_type list_resource_type_dependents

Organization (8)

get_organization create_custom_attribute update_custom_attribute delete_custom_attribute list_organization_members list_custom_attributes get_organization_settings update_organization_settings

Viewer (1)

get_viewer

Audit Logs (3)

get_audit_log list_audit_logs list_audit_log_event_types

Groups (14)

list_groups get_group create_group update_group delete_group add_group_user remove_group_user revoke_group_invitation add_group_service_account remove_group_service_account list_group_members list_group_service_accounts list_group_invitations list_group_policies

Service Accounts (4)

list_service_accounts get_service_account update_service_account delete_service_account

Service account creation is deliberately not exposed — the MCP server can never mint new credentials.

OCI Repos (8)

list_oci_repos get_oci_repo create_oci_repo update_oci_repo delete_oci_repo create_oci_repo_grant delete_oci_repo_grant list_oci_repo_grants

Policies (11)

get_policy create_policy update_policy delete_policy list_policy_actions list_policy_entities evaluate_policy evaluate_policies_batch explain_policy get_policy_attribute_schema list_policy_attribute_values

Server (1)

get_server

URLs (1)

get_url

Contributing

Development, architecture, and release documentation lives in CONTRIBUTING.md.

License

MIT

Source: README.md at commit 973d9be

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.2.0LatestSep 23, 2026
  2. v0.1.7Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts