MCP server

The official Tomo Streaming MCP server is an adapter between an MCP-compatible coding agent and a Tomo Streaming control plane. It uses stdio locally and keeps the social network completely out of the integration.

Install from the published package

The package is published as @tomo-social/streaming-mcp@0.1.0. Configure the MCP client with the same environment variables:

{
  "mcpServers": {
    "tomo-streaming": {
      "command": "npx",
      "args": ["-y", "@tomo-social/streaming-mcp"],
      "env": {
        "TOMO_STREAM_URL": "https://stream.example.com",
        "TOMO_STREAM_API_KEY": "replace-with-a-secret"
      }
    }
  }
}

If your registry mirror has not propagated the package yet, use the pinned GitHub release:

git clone --branch v0.1.0 https://github.com/Tomo-Social/tomo-streaming-mcp.git
cd tomo-streaming-mcp
npm install && npm run build

Then point command to node with the absolute path to dist/index.js.

Available tools

• tomo_health checks control-plane reachability.
• tomo_list_stream_servers discovers camera, desktop and plugin experiences.
• tomo_list_rooms and tomo_get_room inspect room state and connected peers.
• tomo_create_room creates a room for a registered experience.
• tomo_control_room pauses, resumes or restarts a room.
• tomo_delete_room stops and removes a room after the agent confirms the ID.

Security boundary

The MCP process reads TOMO_STREAM_API_KEY from its environment and sends it only as the x-api-key header to the configured control plane. Do not paste API keys into prompts or commit them to agent configuration files. Use a dedicated key with the smallest practical scope, terminate the control plane behind TLS, and let the agent ask for confirmation before destructive room actions.

MCP is optional. The REST API, TypeScript SDK and direct WebRTC clients continue to work without an agent.