Skip to main content

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:
Restart Claude Desktop after saving.
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:
Add SocQ for your user account on macOS, Linux, or WSL:
On native Windows, wrap npx with cmd /c:
Start Claude Code from the same environment so the bridge inherits SOCQ_API_KEY.
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:
For Claude Code on macOS, Linux, or WSL, include the same filter when adding the server:
On native Windows, insert cmd /c before npx. See Choose MCP tools for mode selection and filtering limits.

Verify

For Claude Code, first confirm that the server is registered:
Then ask Claude Desktop or Claude Code:
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, Anthropic’s Claude Desktop local MCP guide, and the Claude Code MCP guide.