Tomo Streaming MCP

Use Tomo Streaming from Codex, Claude Code, Cursor, Windsurf, Antigravity and other MCP-compatible agents.

The server runs locally over stdio and calls a Tomo Streaming control plane over HTTP. It exposes room and runtime operations without coupling an agent to the social network.

Setup

npm install
npm run build

Set the control-plane URL and API key in the MCP client's environment:

{
  "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 npm registry mirror has not propagated the package yet, install the pinned GitHub release instead:

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

For a local checkout, replace npx with node and the absolute path to dist/index.js.

Related MCP server: OpenMesha

Tools

Security

The API key is read only from the process environment and is never returned as tool output. Run the MCP server with the minimum control-plane permissions and keep the control plane behind TLS. Deleting rooms is exposed as an explicit tool so an agent can request confirmation in its own UI.

Compatibility

MCP is the integration boundary. The same server configuration works with Codex, Claude Code, Cursor, Windsurf, Antigravity and any client that supports MCP stdio servers. The control plane and streaming SDK remain usable without MCP.

License

Source-available under the PolyForm Noncommercial License. Commercial agent integrations require a separate license from Tomo.