> ## Documentation Index
> Fetch the complete documentation index at: https://docs.molesignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Claude Code

> Connect Claude Code to MoleSignal Inbound MCP with remote HTTP, OAuth, project scopes, or an API token.

Claude Code supports remote Streamable HTTP servers, OAuth discovery, and local, project, or user
configuration scopes.

## Connect with OAuth 2.1

<Steps>
  <Step title="Add the remote server">
    ```bash theme={null}
    claude mcp add --transport http --scope user \
      molesignal https://molesignal.example.com/api/v1/mcp
    ```

    `--scope user` makes the server available across projects. Omit the flag for local project
    state, or use `--scope project` to write a shared `.mcp.json` entry.
  </Step>

  <Step title="Authorize MoleSignal">
    ```bash theme={null}
    claude mcp login molesignal
    ```

    Alternatively, open Claude Code, run `/mcp`, select `molesignal`, and complete authentication.
  </Step>

  <Step title="Verify the server">
    ```bash theme={null}
    claude mcp get molesignal
    claude mcp list
    ```
  </Step>
</Steps>

For an SSH or headless terminal, print the authorization URL and paste the final callback URL back
into Claude Code:

```bash theme={null}
claude mcp login molesignal --no-browser
```

## Connect with an API token

Use environment expansion in a project `.mcp.json` instead of committing a token:

```json theme={null}
{
  "mcpServers": {
    "molesignal": {
      "type": "http",
      "url": "https://molesignal.example.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${MOLESIGNAL_MCP_TOKEN}"
      }
    }
  }
}
```

Set `MOLESIGNAL_MCP_TOKEN` before starting Claude Code. Project-scoped servers require an explicit
trust decision before the first connection.

See the [official Claude Code MCP documentation](https://code.claude.com/docs/en/mcp).