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

# Claude Desktop

> Configure ScrapeGraph MCP in Claude Desktop

## Claude Desktop Setup

Claude Desktop connects to MCP servers over stdio, so the hosted endpoint is reached through the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) proxy.

Add this to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):

```json theme={null}
{
  "mcpServers": {
    "sgai": {
      "command": "npx",
      "args": [
        "mcp-remote@0.1.38",
        "https://mcp.scrapegraphai.com/mcp"
      ]
    }
  }
}
```

<Note>
  `npx` requires Node.js on your `PATH`. Pinning the version keeps the setup reproducible — drop the `@0.1.38` suffix if you would rather always take the latest proxy.
</Note>

## Authenticate

Restart Claude Desktop after saving the configuration. The first connection starts the login and opens a browser window: choose **Continue with Google** and sign in with the Google account associated with your ScrapeGraphAI account.

Once the browser confirms the connection, return to Claude Desktop — the tools are ready.

### With an API key instead

Pass the key as a header and let the proxy forward it, which skips the OAuth flow:

```json theme={null}
{
  "mcpServers": {
    "sgai": {
      "command": "npx",
      "args": [
        "mcp-remote@0.1.38",
        "https://mcp.scrapegraphai.com/mcp",
        "--header",
        "Authorization:${SGAI_AUTH_HEADER}"
      ],
      "env": {
        "SGAI_AUTH_HEADER": "Bearer YOUR_API_KEY"
      }
    }
  }
}
```

<Note>
  The header value is split across `args` and `env` on purpose. On Windows, Claude Desktop does not escape spaces inside `args`, so keeping `Authorization:${SGAI_AUTH_HEADER}` free of spaces avoids a mangled header.
</Note>

## Verify

Ask Claude to run the `credits` tool. A balance response confirms that authentication and tool execution both work.

<Tip>
  See the [tool reference](/services/mcp-server/introduction#available-tools) for everything the server exposes.
</Tip>