X Twitter Scraper API For Tweets, Followers, MCP

Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.

Framer shows Xquik MCP with Claude Code, Codex, Cursor, and more

Featured in Framer
_{Watch Connect Framer to Claude Code, Codex, Cursor, and more at 6:07 to see Xquik MCP in action.}

Xquik is a production Twitter/X scraper API and X API alternative for teams that need structured X data at scale: tweet search, profiles, followers, following, engagement, media, lists, communities, trends, monitors, webhooks, exports, MCP tools, SDKs, and confirmation-gated X actions.

This repository packages Xquik as an AI agent skill for Claude Code, OpenAI Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, and other skills-compatible agents. It helps agents choose the right REST endpoint, MCP tool, SDK, webhook, extraction, export, or approval-gated workflow without guessing.

Includes 100+ REST API endpoints (123 documented operations), 2 MCP tools, HMAC webhooks, 23 bulk extraction tools, Xquik SDK pointers, and confirmation-gated write actions.

Why Teams Use Xquik

Replace fragmented Twitter scraper tools with one X data API for reads, exports, monitors, webhooks, SDKs, MCP, and gated writes.
Ship X data integrations faster with endpoint routing for tweet search, user lookup, timelines, followers, replies, quotes, retweeters, favoriters, media, lists, communities, articles, trends, and Spaces.
Build production apps, not just dataset runs with REST APIs, typed SDKs, OpenAPI, MCP tools, cursor pagination, webhook delivery, and exports.
Control large jobs before they run with usage estimates for extractions, draws, monitors, webhooks, and other metered workflows.
Keep agents safe around X content with API-key-only auth, read-only defaults, untrusted-content delimiters, and explicit approval for private reads, writes, persistent resources, and bulk jobs.
Support enterprise-scale X data pipelines with high-throughput read limits, bulk extraction jobs, exports, event replay, and webhook automation.
Win high-intent search traffic for Twitter scraper API, X scraper, X API alternative, tweet search API, Twitter follower export, social listening API, X monitoring, and X automation.

What You Can Scrape From X Twitter

Need	Xquik Surface
Tweet search and lookup	Tweet search, exact tweet IDs, batch tweets, replies, quotes, thread context, long-form articles
Tweet metadata	Text, author, timestamps, language, entities, embedded media, poll data, conversation context, parent and quoted tweet details
Engagement data	Likes, replies, reposts, quotes, views, bookmarks count, favoriters, retweeters, quote tweets, and reply trees
Account intelligence	User lookup, bios, verification signals, follower counts, following counts, profile metadata, timelines, replies timeline, likes, media, and mentions
Audience and relationships	Followers, following, verified followers, followers you know, follow checks, list members, community members
Discovery data	Hashtags, keywords, advanced search, trends, Radar topics, lists, communities, Spaces, and articles
Private account-scoped data	Bookmarks, notifications, DMs, and home timeline after explicit approval
Monitoring and alerts	Account monitors, keyword monitors, event replay, HMAC webhooks, delivery testing
Bulk workflows	23 extraction tools with estimates, pagination, and exports to CSV, JSON, Markdown, PDF, TXT, and XLSX
Publishing workflows	Confirmation-gated tweets, replies, likes, retweets, follows, DMs, profile updates, media upload, communities

Start From Any X Input

Use profile URLs, @handles, user IDs, tweet URLs, tweet IDs, search queries, hashtags, list IDs, community IDs, Space IDs, article tweet IDs, webhook destinations, or bulk target lists. Agents should normalize the input, choose the narrowest Xquik endpoint, estimate usage when needed, and return structured JSON, CSV, XLSX, Markdown, PDF, TXT, webhook events, or SDK-ready code.

Twitter Scraper API Use Cases