X Twitter Scraper

What Xquik-dev/x-twitter-scraper MCP server does

The Xquik-dev/x-twitter-scraper MCP server connects AI clients to Xquik’s hosted X (Twitter) API. It covers public data retrieval, bulk extraction, monitoring, and selected actions on connected X accounts. The service is independent of X Corp and is not the official X API.

The API supports tweet lookup and search, timelines, replies, quotes, threads, likes, reposts, and media. Profile operations include lookup, batch lookup, search, followers, following, relationships, account details, and availability. Other supported resources include lists, communities, trends, Spaces, articles, bookmarks, notifications, and feeds.

How it works

Connect an MCP-compatible client to the hosted StreamableHTTP endpoint at https://xquik.com/mcp. The server exposes route discovery and bounded execution through MCP tools. The README identifies the hosted operations as docs, search, and execute; the listing describes 121 endpoints available through two tools.

Requests use an Xquik API key. Public reads can run without an official X developer account or a connected X account. Private reads and actions require a connected account. Never provide an X password, cookie, session export, or two-factor authentication code to Xquik or an agent.

Search responses can include tweet text, timestamps, engagement counts, author information, pagination state, and diagnostics. Results may be filtered on the server, and callers should continue with next_cursor while has_next_page is true. A filtered page can contain no tweets while still having another page.

Setup and configuration

Create an API key in the Xquik dashboard and provide it as XQUIK_API_KEY. The REST examples send it in the x-api-key header. For MCP, the client table lists OAuth or an Xquik API key as the credential options.

The repository also contains portable agent Skills and plugin metadata. Its documented installation paths include Skills, Codex plugins, Gemini CLI, LobeHub, and shadcn-based workflows. Cursor is shown in the project’s client demonstration. The hosted MCP endpoint is the relevant connection target when an MCP client is being configured directly.

Tools and capabilities

The Xquik-dev/x-twitter-scraper MCP server supports:

• Searching and retrieving structured tweets, profiles, followers, replies, and related X resources.
• Running 23 bulk extraction types with estimates, result caps, multiple targets, cursors, and exports.
• Monitoring accounts and keywords, storing events, and receiving signed webhooks.
• Returning data as JSON, CSV, Markdown, PDF, TXT, XLSX, API pages, or webhook events where supported.
• Performing supported actions such as posting, replying, deleting, liking, reposting, following, sending direct messages, handling media, and managing profiles or communities.
• Opening support tickets, exchanging messages, handling attachments, and polling processing status.

Search and extraction use result-based credit billing. The README gives a PAYG rate of $0.00015 per result for the illustrated search operation, with a first funding amount of $10 and unused credits carrying over.

Limitations and notes

Deleted, protected, restricted, or otherwise unavailable content may not be accessible. Optional fields are omitted when X does not provide them, and the service states that it does not invent missing content. Private data and account actions depend on a connected X account.

The service is separate from X Corp, and the exact behavior of individual operations is defined by Xquik’s live API contract. Choose the official X API instead when its exact contract, support, or platform relationship is a requirement.