# MeatSpace MCP server

Human-in-the-loop for AI agents. Submit choices, get a human decision.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-zmarten-meatspace
- Repository: https://github.com/zmarten/meatspace
- Website: https://meatspace.run

## Install
- Endpoint: https://meatspace.run/api/mcp
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: Authorization (secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://meatspace.run/api/mcp
- Header: Authorization

## Tools
- get_service_status - Check whether MeatSpace is available and when to use a human. Call this when deciding whether to escalate a subjective or high-consequence choice. Endpoint: https://meatspace.run/api/mcp
- ask_human - Present content to a human and ask them to choose between options. Use this for subjective judgment, approval, preference, or tie-breaks. Avoid using it for deterministic checks or reversible low-stakes choices. The tool waits briefly for a result, then returns pending if the human has not responded yet. Endpoint: https://meatspace.run/api/mcp
- provision_api_key - Create a MeatSpace API key instantly. No authentication required. Returns a Bearer token for use with the ask_human tool. Max 5 active keys per email address. Endpoint: https://meatspace.run/api/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.zmarten
- Version: 0.1.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 7, 2026
- Source: https://registry.modelcontextprotocol.io