Labsco
MCP SERVER

X Twitter Scraper

by Xquik-dev ↗

Read X (Twitter) data from an MCP client — Tweet search, profiles, followers, timelines, replies, bulk exports and keyword monitors — through a hosted endpoint that takes an Xquik API key instead of an official X developer account.

Site Crawling & Scraping Infrastructure
Summary
A vendor data API with an MCP front door — no browser state of your own.

Everything runs on Xquik's side against your API key, so there are no proxies, cookies or X logins to manage, and the filters run before you are billed rather than after. The tradeoff is that coverage, schema and the bill are all theirs: deleted, protected or restricted content can stay out of reach, some bounded reply reads come back as `424` with partial rows and a diagnostic, and the docs do not yet tie every deduplicated row to the final credit deduction — so run the estimate route before a large job and treat what it returns as a forecast, not an invoice.

What it is

Xquik's hosted MCP server at `https://xquik.com/mcp`, sitting in front of the company's own REST API for X (Twitter) data. Xquik is an independent third-party service, not affiliated with X Corp. The MCP surface is a route-discovery surface rather than one tool per endpoint: the exposed names are `docs`, `search` and `execute`, and `execute` takes a path plus a query — a `xquik.request` against `/api/v1/x/tweets/search` carrying `q`, `language`, `minLikes` and `limit`. The live OpenAPI behind it documented 128 HTTP operations when the README was checked against it on 2026-08-23. MCP responses come back with normalized `snake_case` fields; binary support downloads go through REST instead. Current clients negotiate MCP `2026-07-28` through `server/discover`. The same repository is an Agent Plugins v1 package — `x-developer` v2.6.7 bundles the `x-twitter-scraper` and `xquik-social-research` Skills alongside the hosted server.

What you get
  • Tweet reads — lookup, batch lookup, search, timelines, replies, quotes, threads, likes, reposts and media, returning `id`, `text`, `createdAt`, `likeCount`, `retweetCount`, `replyCount`, `quoteCount`, `viewCount`, `bookmarkCount` and an `author` block
  • Profile reads — lookup, batch lookup, search, followers, following, relationships, account details and availability
  • Other X surfaces — Lists, communities, trends, Spaces, articles, bookmarks, notifications and supported feeds
  • Filters applied server-side, before delivery — Tweet filters cover authors, recipients, mentions, languages, dates, media, engagement, verification, phrases, words, hashtags, cashtags, URLs, lists, places, replies, reposts and quotes; profile filters cover follower counts, following counts, Post counts, account age, verification, websites, locations, bios and usernames
  • Bulk extraction across 23 extraction types, with multi-target jobs, result caps, `dedupeAcrossTargets` and `dedupeMode`, cursor pages and file exports
  • A cost estimate you can run first — the estimate route returns `allowed`, `estimatedResults`, `creditsRequired`, `creditsAvailable` and `source`, and consumes no credits
  • Exports in JSON, CSV, Markdown, PDF, TXT and XLSX
  • Account and keyword monitors — active monitors check every second, with stored events and signed webhooks included; webhook deliveries carry `X-Xquik-Timestamp`, `X-Xquik-Nonce` and `X-Xquik-Signature`, and event cursors let you recover after downtime
  • Write actions on a connected X account in the same contract — posts, replies, deletes, likes, reposts, follows, DMs, media, profiles and communities
  • Support-desk calls — create tickets, send messages, upload and download attachments, poll processing status
Requirements

An `XQUIK_API_KEY`, created in the Xquik dashboard; an MCP client authenticates with OAuth or that API key. You do not need an official X developer account, and you do not need to connect an X account at all for Tweet, profile, search, follower, timeline, reply, quote, repost or media scraping. Private reads and X account actions are the exception — those need an X account connected first. Never send an X password, cookie, session export or 2FA code to Xquik or to an agent; the Skill does not install packages, run local bridge commands, write local files, browse local networks or load remote code. Billing is per delivered result and runs on credits: 1 credit per returned Tweet on search, 1 credit per result for most extraction rows, 5 credits per article extraction row, and no credits for estimates or for reading and exporting a stored job. The PAYG rate is $0.00015 per credit, the first PAYG funding amount is $10, and unused credits carry over. Each active monitor costs 21 credits per hour. A low balance can stop results at the affordable count; zero affordable results return `402 insufficient_credits`.

Setup effort

One command plus a key — npx -y x-developer, then supply credentials