Skip to content
MCP Server Directory logo
communication-collaboration

Xquik MCP Server

Remote MCP server for X and Twitter automation: tweet search, profile tweets, follower export, media workflows, webhooks, and confirmation-gated posting via Xquik.

Reviewed overview

MCP 服务器概览

What is Xquik MCP Server? Xquik MCP Server is a remote Model Context Protocol (MCP) server and API layer for interacting with X/Twitter data and automations. It exposes scoped REST-like tools (explore and xquik) over Streamable HTTP so AI agents, IDEs, and client apps can search tweets, read profiles and timelines, export followers, run media workflows, set up webhooks, and perform confirmation-gated writes (posting, DMs, likes) via Xquik.

How to use Xquik MCP Server?

  • Endpoint: connect to https://xquik.com/mcp using an MCP-capable client or SDK.
  • Authenticate: OAuth 2.1 (recommended) or API key fallback (x-api-key / Authorization header) for clients without OAuth.
  • Tools: use the explore tool for read-only catalog discovery and the xquik tool for executing authenticated API calls inside a sandboxed JS function (xquik.request(path, options)).
  • Clients & SDKs: supported in Claude, Codex (with fallback notes), Cursor, VS Code, Gemini, Copilot CLI and many editor/IDE/agent SDKs. SDKs and language bindings available (TypeScript, Python, Go, Java, Kotlin, C#, Ruby, PHP, CLI, Terraform).
  • Alternatives: use REST API for backend services, binary downloads, guest wallet flows, or fine-grained control; use MCP for agent/IDE interactions.

Key features

  • MCP v2.6.0 by Streamable HTTP with compatibility discovery (.well-known/mcp.json).
  • Two sandboxed tools: explore (free, read-only catalog) and xquik (authenticated calls, may mutate).
  • Scoped catalogs: full-account credentials expose ~120 MCP routes; guest paid_reads expose exactly 33 GET read routes.
  • OAuth 2.1 support (CIMD, DCR, PKCE) and API-key fallback for non-OAuth clients.
  • Agent/IDE integrations, example prompts, and framework guides (LangChain, CrewAI, Pydantic AI, Google ADK, etc.).
  • Export and extraction workflows (CSV/JSON/XLSX), media upload workflows, webhooks with signature verification, and billing/usage controls.
  • Sandbox code-execution model (async JS arrow functions run server-side with injected auth).
  • Xquik “Skill” package for agents to get API knowledge without direct MCP connection.

Use cases

  1. Monitor accounts and webhooks for new tweets and replies and replay stored events.
  2. Search and extract tweet threads, replies, quote tweets, and export to CSV/JSON/XLSX for analysis or CRM ingestion.
  3. Automate campaigns: follower exports, giveaways, campaign verification, and audience discovery workflows.
  4. Compose, optimize and send tweets or DMs using agent-driven drafting with confirmation gating before posting.
  5. Integrate into agent-driven IDEs to let LLMs query X data, draft messages, and invoke authenticated actions safely.
  6. Build dashboards/backends using REST for binary downloads or guest wallet flows while using MCP for agent interactions.

FAQ (from the docs)

  • Do I need an X account to use Xquik? Public reads require no connected X account; any write action (post, DM, etc.) requires a connected X account and proper credentials.

  • What authentication methods are supported? OAuth 2.1 is recommended (CIMD/DCR/PKCE). API keys are supported as a fallback but must be stored securely; guest paid_reads keys have limited GET-only access.

  • When should I use MCP vs REST? Use MCP for AI agents and IDE integrations where agents run code against the catalog. Use REST for backend services, file downloads, guest wallet credential routes, and fine-grained control.

  • Can MCP download binary attachments? No — MCP rejects binary responses; use the REST download endpoints for private support attachments and media downloads.

  • What are guest paid_reads limits? Guest sessions expose exactly 33 eligible GET paid-read routes and cannot execute mutations or non-eligible routes. Guest wallet checkout/top-up flows are REST-only.

  • Are there rate limits and billing? Yes — Xquik documents rate limits, credits, billing, and paid-read behaviors. Follow the billing and guest-wallet guides before starting paid extraction or checkout flows.

  • Is Xquik affiliated with X Corp/Twitter? No. Xquik is an independent third-party service (see Non-Affiliation Notice).

  • Where to get help or docs? Full docs and guides: https://docs.xquik.com/mcp/overview. Support: support@xquik.com. GitHub: https://github.com/Xquik-dev.