Install mumo in any MCP client.

Find your client's MCP settings

Create a remote MCP server entry named mumo. Choose HTTP or Streamable HTTP if your client asks for a transport. mumo does not require a local stdio process for the generic setup.

Add the mumo server config

Use this full config shape, including the Authorization header. Leave the placeholder key in place for now. You will generate the real key in the next step, then reload your client so it can discover the mumo tools.

{
  "mcpServers": {
    "mumo": {
      "url": "https://mumo.chat/api/mcp",
      "headers": {
        "Authorization": "Bearer mmo_live_YOUR_KEY_HERE"
      }
    }
  }
}

Some clients use servers instead of mcpServers, or store this in a TOML file instead of JSON. Some also nest headers differently. Use your client's naming, but keep the endpoint URL and Authorization header the same. See the MCP docs for client-specific examples.

Generate your API key

Sign in, create a mumo API key, and copy the value that starts with mmo_live_. Replace the placeholder in your MCP client's Authorization header, or paste it into the client's secret-storage prompt.

Prefer to inspect the tool schema first? Browse the MCP docs.

Reload and verify the tools appear

Restart your agent app or reload its MCP configuration. The mumo tools should now appear in your client's MCP tool list: create_deliberation, append_round, wait_for_round, get_session, and others.

If the tools do not appear, check that the Authorization header contains your real API key, then inspect your client's MCP logs. Most clients expose them under a logs, developer tools, or output panel. For client-specific config examples, see the MCP docs.

Run your first deliberation

Once your key is in place, ask your agent to use mumo on a contested decision. Name mumo explicitly the first time so your client routes to the MCP tools.

Ask mumo to compare Postgres and MongoDB for our event store.
Include the constraints from this repo and tell me where the models disagree.