Cursor
The stdio bridge is the most portable Cursor configuration and works without a separate OAuth flow.
Prerequisites
- Node.js 20 or later;
- a SocQ API key;
- a current Cursor release with MCP support.
Open Cursor’s MCP settings, add a local server, and use:
This local configuration contains a credential. Do not commit or share it.
If your Cursor version supports authenticated Streamable HTTP with environment-backed bearer tokens, it can connect to https://api.socq.ai/mcp directly. Keep the stdio configuration when remote authentication is unavailable.
To expose typed YouTube tools, change the server name and arguments:
See Choose MCP tools for mode selection and filtering limits.
Verify
Restart the SocQ MCP server in Cursor, then ask:
The connection is working when Cursor discovers the SocQ tools, calls socq_account, submits the collection, and reads the returned task with socq_get_task.
Troubleshoot
Restart the server after configuration changes so Cursor refreshes the tool list. See Troubleshooting integrations for authentication, missing-tool, and task errors.