# Claude

This page covers the supported BoldSign MCP Server setup paths for **Claude Web**, and **Claude Code**.

## Claude Web

The hosted BoldSign MCP server is best connected to Claude Web as a remote connector. The OAuth authentication is the only supported method for this setup.

### Preparation

- Create or update a {% customlink href="/authentication/oauth-2-0/" text="BoldSign OAuth application" /%} in the same region as your MCP endpoint.
- Anthropic documents `https://claude.ai/api/mcp/auth_callback` and `https://claude.com/api/mcp/auth_callback` as the hosted Claude redirect URIs for remote MCP authentication. Add these redirect URIs to your BoldSign OAuth application before you start the connector setup.
- Remote connector availability depends on the Claude plan and features available in your environment.

### Setup steps

1. Open Claude Web and navigate from the sidebar **Customize** → **Connectors**.
2. Click **+** to add a custom connector.
3. Provide a name and the BoldSign MCP endpoint from Overview for your region.
4. Expand **Advanced Settings**, add the Client ID and Client Secret from your BoldSign OAuth application and Click **Add**.
5. Click "Connect" and complete the sign-in flow Claude presents for the connector.
6. Enable the connector for the conversation where you want to use BoldSign tools.

## Claude Code

Claude Code supports remote HTTP MCP servers natively, making it a natural fit for the hosted BoldSign MCP server. The recommended approach uses an environment variable for the API key and a project-level `.mcp.json` file so the configuration is portable and the key is never stored in source control.

```json
{
    "mcpServers": {
        "boldsign": {
            "type": "http",
            "url": "<YOUR_REGION_MCP_ENDPOINT>",
            "headers": {
                "X-API-Key": "${BOLDSIGN_API_KEY}"
            }
        }
    }
}
```

Replace `<YOUR_REGION_MCP_ENDPOINT>` with the endpoint for your region from the {% customlink href="/boldsign-mcp-server/overview/#production-regional-endpoints" text="Regional Endpoints" /%}. The `${BOLDSIGN_API_KEY}` placeholder is expanded from your shell environment at runtime, Claude Code does not store the literal key value.

After saving the file:

1. Start Claude Code in that project.
2. Open `/mcp` to confirm that the `boldsign` server connected and exposed tools.
3. Use a read-only prompt first to verify the connection.
