Setup

The LoomBrain MCP server runs at https://mcp.loombrain.com/mcp and uses the HTTP transport. No local process or proxy is required.

Claude Code

Run this command once in your terminal:

claude mcp add --transport http loombrain https://mcp.loombrain.com/mcp -s user

The -s user flag registers the server at the user scope, making it available in all Claude Code sessions without repeating the setup per project.

Claude Desktop

Open or create ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) and add the loombrain entry:

{
  "mcpServers": {
    "loombrain": {
      "type": "url",
      "url": "https://mcp.loombrain.com/mcp"
    }
  }
}

Restart Claude Desktop after saving the file.

Cursor

Add a .mcp.json file in your project root:

{
  "mcpServers": {
    "loombrain": {
      "type": "url",
      "url": "https://mcp.loombrain.com/mcp"
    }
  }
}

This is also the format used when sharing MCP configuration across a team via a project-level .mcp.json checked into version control.

First use and authentication

The first time any client sends a request to the MCP server, it triggers an OAuth 2.1 authorization flow:

1. A browser window opens and redirects to the LoomBrain sign-in page.
2. After signing in (Google or email), authorization is granted to the MCP server.
3. Access and refresh tokens are stored in your system keychain.

Subsequent requests use the stored tokens. Refresh happens automatically — you will not be prompted again unless you revoke access or sign out.

If browser-based sign-in is not possible in your environment (CI, remote server), use an API key instead. See Authentication for details.