Massed MCP Server

Massed MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Stdio bridge to the hosted Massed Compute MCP endpoint — a verbatim JSON-RPC pass-through.

What you get

The packages published from this repo are a verbatim proxy of the public MCP endpoint at https://vm.massedcompute.com/api/mcp — zero added surface. Every JSON-RPC message (initialize, tools/list, tools/call, resources/list, resources/read, ping, …) is forwarded unchanged with your stored API key injected as a Bearer header, and responses come back unchanged. Nothing is added, renamed, filtered, or rewritten on the way through:

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 2 environment variables: MASSED_COMPUTE_API_KEY, MASSED_COMPUTE_API_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the massed mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by yung00se; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Massed's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.