Meatspace MCP Server

Human-in-the-loop service for AI agents. When an agent hits a subjective, high-stakes, or ambiguous decision, MeatSpace routes it to a human who

Local serverstdio

What is the Meatspace MCP server?

Meatspace MCP server exists for a simple reason — assistants are far more useful when they can act on Meatspace directly instead of describing what you should do. Human-in-the-loop service for AI agents. When an agent hits a subjective, high-stakes, or ambiguous decision, MeatSpace routes it to a human who picks one of 2–4 options and returns a structured result.

What you get

  • Approval gates before destructive or irreversible actions (deploys, deletes, payments)
  • Subjective tie-breaks where the model is below its confidence threshold
  • Tasteful judgment calls — copy choices, design preferences, ranking ties
  • Escalation when an agent has run out of deterministic checks

What the assistant can call

Once Meatspace is connected, these are the calls the assistant has available:

  • get_service_status — availability and escalation guidance. No auth
  • provision_api_key — mint a Bearer token. No auth, rate-limited
  • ask_human — submit a decision. Requires Bearer auth
  • Method — Endpoint
  • MCP — POST /api/mcp (Streamable HTTP)
  • Path — Format

Configuration and credentials

You will need one environment variable: MEATSPACE_API_KEY. 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.

Setting it up

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Meatspace's toolset — get_service_status, provision_api_key, ask_human and 3 more — is a fair guide to whether it matches your workflow. It is maintained by zmarten; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • 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 meatspace mcp server does with a few real requests.

Available tools

ToolWhat it does
get_service_statusavailability and escalation guidance. No auth.
provision_api_keymint a Bearer token. No auth, rate-limited.
ask_humansubmit a decision. Requires Bearer auth.
MethodEndpoint
MCPPOST /api/mcp (Streamable HTTP)
PathFormat

How to install the Meatspace MCP server

{
  "mcpServers": {
    "meatspace": {
      "command": "npx",
      "args": ["-y", "npm"],
      "env": {
        "MEATSPACE_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MEATSPACE_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Meatspace to get service status.
  • Use Meatspace to provision api key.
  • Use Meatspace to ask human.

Frequently asked questions

It connects Meatspace to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (get_service_status, provision_api_key, ask_human, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Meatspace directly.