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

# Claude

> Connect Claude Desktop or Claude Code to SocQ MCP and verify a collection.

# Claude

Claude Desktop and Claude Code can run the published `@socq/mcp` bridge as a local stdio server. The bridge forwards tool discovery and calls to the hosted SocQ MCP endpoint.

## Prerequisites

* a SocQ API key;
* Node.js 20 or later;
* a current Claude Desktop or Claude Code installation.

## Configure Claude Desktop

Open the Claude Desktop developer configuration and add:

```json theme={"system"}
{
  "mcpServers": {
    "socq": {
      "command": "npx",
      "args": ["-y", "@socq/mcp"],
      "env": {
        "SOCQ_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
```

Restart Claude Desktop after saving.

> [!WARNING]
>
> This local configuration contains a credential. Do not commit or share it. For a distributed integration, package the bridge as a desktop extension and mark the API-key field as sensitive so Claude can use operating-system secure storage.

## Configure Claude Code

Set `SOCQ_API_KEY` in the shell that starts Claude Code:

```bash theme={"system"}
export SOCQ_API_KEY="YOUR_API_KEY"
```

```powershell theme={"system"}
$env:SOCQ_API_KEY="YOUR_API_KEY"
```

Add SocQ for your user account on macOS, Linux, or WSL:

```bash theme={"system"}
claude mcp add socq --scope user -- npx -y @socq/mcp
```

On native Windows, wrap `npx` with `cmd /c`:

```powershell theme={"system"}
claude mcp add socq --scope user -- cmd /c npx -y @socq/mcp
```

Start Claude Code from the same environment so the bridge inherits `SOCQ_API_KEY`.

> [!WARNING]
>
> Keep the API key in your environment. Do not pass it through `--env`, because that stores the literal value in Claude Code's MCP configuration.

## Limit the tool list

For Claude Desktop, add a platform filter to the bridge arguments:

```json theme={"system"}
"args": ["-y", "@socq/mcp", "--platforms", "youtube"]
```

For Claude Code on macOS, Linux, or WSL, include the same filter when adding the server:

```bash theme={"system"}
claude mcp add socq-youtube --scope user -- npx -y @socq/mcp --platforms youtube
```

On native Windows, insert `cmd /c` before `npx`. See [Choose MCP tools](https://docs.socq.ai/integrations/mcp-filtering) for mode selection and filtering limits.

## Verify

For Claude Code, first confirm that the server is registered:

```bash theme={"system"}
claude mcp get socq
```

Then ask Claude Desktop or Claude Code:

```text theme={"system"}
Use SocQ to check my account, then collect the latest 20 comments from this
YouTube video. Wait for the task to finish and return the results as a table:
https://www.youtube.com/watch?v=VIDEO_ID
```

The connection is working when Claude discovers the SocQ tools, calls `socq_account`, submits the collection, and reads the returned task with `socq_get_task`.

## Troubleshoot

* Claude Desktop: restart the app after configuration changes so it refreshes the tool list.
* Claude Code: use `claude mcp list` to inspect configured servers and `/mcp` to view connection status. Restart it if `SOCQ_API_KEY` was set after launch.

See [Troubleshooting integrations](https://docs.socq.ai/integrations/troubleshooting), Anthropic's [Claude Desktop local MCP guide](https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop), and the [Claude Code MCP guide](https://docs.anthropic.com/en/docs/claude-code/mcp).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.