MuseLabs MCPSetup

Connect your AI client

Add this server to your client, then sign in with MuseLabs (email or Google). No API keys to copy.

https://mcp.muselabs.ai/mcp

Claude Code

One command — a browser opens to sign in with MuseLabs:

claude mcp add --transport http muselabs https://mcp.muselabs.ai/mcp

Your MuseLabs tools are then available in any Claude Code session.

OpenAI Codex CLI

Add to ~/.codex/config.toml (Codex supports OAuth for HTTP servers):

[mcp_servers.muselabs]
url = "https://mcp.muselabs.ai/mcp"

Codex prompts you to sign in on first use — or run codex mcp add.

Gemini CLI

One command — adds it to ~/.gemini/settings.json:

gemini mcp add --transport http muselabs https://mcp.muselabs.ai/mcp

OpenClaw

OpenClaw manages MCP servers with MCPorter. Add this to ~/.openclaw/workspace/config/mcporter.json — the mcp-remote bridge runs the MuseLabs sign-in for you:

{
  "mcpServers": {
    "muselabs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.muselabs.ai/mcp"]
    }
  }
}

Restart the OpenClaw gateway after saving. MCPorter caches the OAuth token in ~/.mcporter/credentials.json.

Hermes Agent

Hermes (Nous Research) speaks remote MCP with OAuth natively. Add to your config.yaml:

mcp_servers:
  muselabs:
    url: "https://mcp.muselabs.ai/mcp"
    auth: oauth

Hermes opens the MuseLabs sign-in and refreshes the token automatically (MCP client support since v0.2.0).

Cursor, Claude Desktop & more

Any MCP client that runs a command-based server works through the mcp-remote bridge, which handles the MuseLabs sign-in for you:

{
  "mcpServers": {
    "muselabs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.muselabs.ai/mcp"]
    }
  }
}

Drop that into the client's MCP config — the universal fallback for any MCP-capable client.