MCP quickstart

Use SocQ MCP to collect social data from Claude, Cursor, Codex, VS Code, or another MCP-compatible client. Configure the server once, then describe the data you need in natural language.

Before you start

You need:

a SocQ API key;
an MCP-compatible client;
Node.js 20 or later only when using the stdio bridge.

Keep the key out of URLs and committed configuration. See Integration authentication.

Connect SocQ

Choose the transport supported by your client:

Transport	Configuration	Best for
Remote MCP	`https://api.socq.ai/mcp`	Clients that support authenticated Streamable HTTP
stdio bridge	`npx -y @socq/mcp`	Clients that run local stdio servers

For the exact configuration, use the guide for Claude, Cursor, Codex, or VS Code.

Complete your first collection

After connecting, ask your client:

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 the client discovers the SocQ tools, calls socq_account, submits the collection, and reads the returned task with socq_get_task.

Next steps

Choose MCP tools to select compact, platform, or exact-tool mode.
Tasks and results for waiting, safe retries, pagination, and raw files.
Troubleshooting integrations for connection and execution errors.

Attribute Agent Skill executions

When an Agent Skill submits through compact or typed MCP, include _request_source: "skill" in the execution arguments. SocQ records the task with request_source="skill-mcp". Normal remote and stdio MCP calls remain mcp-remote and mcp-stdio.

​MCP quickstart

​Before you start

​Connect SocQ

​Complete your first collection

​Next steps

​Attribute Agent Skill executions