Skip to main content
Use https://xquik.com/mcp for authenticated X/Twitter actions. Use https://docs.xquik.com/mcp for public documentation, without authentication. See MCP setup for the full client examples.

​
Current client releases

We checked these official releases on October 1, 2026. Versions below record that review. Install your client’s latest stable release before setup. These paths describe vendor support. Complete Xquik authorization before calling paid tools. For Codex & ChatGPT, follow the OpenAI setup guides.

​
Codex

Current Codex supports Xquik OAuth with the shared local MCP configuration:
Complete sign-in & authorization in your browser. The CLI, app & IDE extension share the host’s MCP configuration. See OpenAI setup & Codex MCP. For API keys, use environment-backed authentication.

​
Claude Code

Add Xquik to your user configuration:
Use --scope project to share the URL through .mcp.json. Claude Code asks you to approve project servers before connecting. Use /mcp inside a session to authenticate or reconnect. Version 2.1.286 fixes stale MCP discovery & repeated authentication reminders. It also fixes credential redaction in MCP errors. Upgrade before diagnosing those symptoms. Version 2.1.287 keeps managed permissions for all MCP tool names. Xquik supports automatic registration. Leave client ID & client secret unset. For API-key headers, .mcp.json expands ${XQUIK_API_KEY} from your environment. See Claude Code MCP.

​
Cursor

Keep the existing URL entry in ~/.cursor/mcp.json or .cursor/mcp.json:
Current Cursor CLI docs use the agent command:
Approve the server when prompted. Team distribution does not automatically enable it. Enterprise policy may restrict servers. Xquik needs no static OAuth auth object. API-key headers use ${env:XQUIK_API_KEY}. Remote entries cannot load envFile. See Cursor MCP configuration.

​
OpenCode

Add this entry to opencode.json:
Then authenticate & check discovery:
OpenCode automatically registers the client & refreshes OAuth tokens. For connection failures, run opencode mcp debug xquik. An API-key entry needs "oauth": false & Bearer {env:XQUIK_API_KEY}. See OpenCode MCP servers.

​
Pi

Pi 1.0.0 has native MCP. No community adapter is required. If your build lacks pi mcp, run pi update self before setup.
Pi stores global servers in ~/.pi/agent/mcp.json. Use --local for .pi/mcp.json; project trust is required. Pi supports Streamable HTTP, not legacy SSE. Use /mcp to inspect connections & /reload after changing external configuration. Pi 1.0.0 validates OAuth callback issuers & stores credentials per server name & URL. Different server names at the same URL need separate sign-ins. Pi’s default codemode exposure makes tools available through tool search & scripts. Use --exposure direct when adding Xquik to expose its 3 tools directly. Pi’s exposure setting is separate from Xquik’s tool mode. For an environment-backed API key:
Set XQUIK_API_KEY before starting Pi. This replaces OAuth for that entry. See Pi’s MCP guide.

​
Copilot CLI, Gemini CLI, Cline & Qwen Code

Current Copilot CLI uses this command:
The URL is positional. Use /mcp to inspect the server & complete authentication. Version 1.0.90 improves discovery recovery & cached OAuth token reuse. See Copilot CLI MCP setup. Gemini CLI & Qwen Code retain httpUrl for manual Streamable HTTP entries:
Gemini uses ~/.gemini/settings.json; Qwen uses ~/.qwen/settings.json. Use their /mcp authentication flow after adding the server. See Gemini MCP & Qwen MCP. Cline CLI uses cline mcp to manage servers & OAuth. Its extension uses the MCP Servers panel. Choose Streamable HTTP & enter https://xquik.com/mcp. The CLI, extension & Desktop app have separate release versions. See Cline MCP.

​
VS Code

Current VS Code recommends portable .mcp.json for new project servers:
Existing .vscode/mcp.json entries still use the top-level servers object. Run MCP: Add Server for guided setup, then approve server trust & OAuth. Managed MCP policies may restrict access. See VS Code MCP setup.

​
Windsurf / Devin Desktop

Current Windsurf documentation calls the editor Devin Desktop. Choose the guide for your active agent. For Devin Local, run:
Current Devin CLI stores servers in dedicated mcp_config.json files. The default local file is .devin/mcp_config.local.json. Use --scope user for your global configuration. See Devin MCP configuration. Legacy Cascade uses mcp_config.json with mcpServers & serverUrl. Open that file through Cascade’s MCP menu to find your installed version’s location. Current macOS & Linux releases use ~/.config/devin/mcp_config.json. Older Windsurf releases used ~/.codeium/windsurf/mcp_config.json. Cascade allows 100 enabled tools total, so prefer Xquik’s default Code Mode. See Cascade MCP configuration.

​
Goose & Roo Code

Goose 1.46.0 fixed the OAuth issuer callback defect. Current 1.52.0 retains that fix. Add a Streamable HTTP extension & complete the browser authorization flow:
See Goose extensions & the issuer fix. Goose also supports environment-backed API-key headers. Roo Code is archived. Its final release supports HTTP headers without MCP OAuth. Use its environment-backed API-key configuration.

​
Check the connection

Confirm the server connects & lists docs, search & execute. Those are Xquik’s default Code Mode tools. Native mode at ?codemode=false exposes individual operations instead. Use xquik-docs as a separate entry for https://docs.xquik.com/mcp. That server needs no OAuth & searches public documentation. A successful Docs MCP connection does not authorize API MCP. See Docs MCP setup. OAuth connections need browser login & consent in each client. Do not copy another client’s token store. For a 401, use the client’s authentication flow. For issuer errors, upgrade the affected client before retrying. Include the UTC time & X-Request-Id when reporting a connection failure.