# Xquik-dev/x-twitter-scraper [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/Xquik-dev/x-twitter-scraper  
**GitHub Stars:** 223  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/xquik-dev-x-twitter-scraper

## Description
Remote X (Twitter) MCP server with 121 endpoints via 2 tools. Post tweets, reply, like, retweet, follow, DM, search, extract data, run giveaways, and monitor accounts. StreamableHTTP at xquik.com/mcp with API key auth.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "x-twitter-scraper": {
    "command": "uvx",
    "args": ["x_twitter_scraper"],
    "env": {
      "XQUIK_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `XQUIK_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Xquik-dev/x-twitter-scraper does

Xquik-dev/x-twitter-scraper gives MCP-compatible agents access to X data and account operations through Xquik. The service covers public data collection and actions performed by a connected X account. Its two MCP tools expose 121 endpoints, including capabilities for:

- Searching Tweets and extracting Tweet, profile, follower, and reply data
- Publishing Tweets and replying to existing posts
- Liking, retweeting, following, and sending direct messages
- Running giveaways
- Monitoring accounts and keywords

The service is positioned as an alternative access path to X data, with REST, MCP, SDK, CLI, webhook, and Actor access available across the broader Xquik platform. This listing concerns the MCP interface.

## How it works

Agents connect to the hosted StreamableHTTP endpoint at `https://xquik.com/mcp` and authenticate with an Xquik API key. The repository also includes a portable Agent Plugins v1 package with bundled Skills and manifests for compatible agents.

Public reads can run without an official X developer account or a connected X account. Private reads and operations that act on X require a connected account. Xquik states that credentials such as an X password, cookie, session export, or 2FA code should not be sent to the service or to an agent.

For data collection, Xquik supports server-side Tweet and profile filters, cursors, result limits, monitors, signed webhooks, and file exports through its platform. Search responses can include Tweet text, timestamps, engagement counts, view and bookmark counts, author details, pagination state, and diagnostics when available.

## Setup and configuration

Create an API key in the Xquik dashboard, then make it available as `XQUIK_API_KEY`. Requests authenticate with the key using the `x-api-key` header. MCP clients should be configured to use the hosted endpoint and provide that credential according to their remote-server configuration.

The repository provides commands for installing its primary Skill:

```bash
bunx skills@1.5.3 add Xquik-dev/x-twitter-scraper
```

It also provides a shadcn registry entry that can be inspected and added separately:

```bash
bunx shadcn@4.18.0 view Xquik-dev/x-twitter-scraper/x-twitter-scraper
bunx shadcn@4.18.0 add Xquik-dev/x-twitter-scraper/x-twitter-scraper
```

## Tools and capabilities

The two MCP tools provide access to the service's 121 endpoints. Supported work includes public X searches, structured data extraction, profile and follower lookups, reply retrieval, Tweet publication, replies, likes, retweets, follows, direct messages, giveaways, and account monitoring.

Searches can use filters such as language, minimum likes, and inclusion or exclusion of replies, retweets, and quotes. Results are paginated with a cursor and can contain fewer records than requested while still indicating that another page is available. Xquik charges for delivered, unique, filter-matching results on its pay-as-you-go service.

## Limitations and notes

Private data and account actions depend on a connected X account. Public reads have different access requirements and do not need an official X developer account. The service is independent of X Corp, and “Twitter” and “X” are X Corp trademarks.

Treat the API key as a secret. Do not provide X passwords, cookies, session exports, or two-factor authentication codes to Xquik or an agent. Choose the official X API instead when an exact official contract, platform support, or direct platform relationship is required.

_Full upstream README: https://allmcps.com/mcp/xquik-dev-x-twitter-scraper/readme_