← Back to directory

Xquik MCP

Community

MCP server for X (Twitter) data extraction and publishing automation

GitHub source repository ↗

★ 188 Stars Category · Dev Tools Very popular Source revision aad8122ed347

51FMRS · D

Reliability

4/20

Security and permissions

8/20

Maintenance

11/20

Documentation

15/20

Setup experience

13/20

The Xquik MCP server offers comprehensive X data access and automation capabilities, suitable for developers building data pipelines or automation tools, but it's non-official and requires attention to compliance and security.

Read the FMRS scoring method →

The Xquik MCP server provides access to X (Twitter) data and account operations, including search, profiles, followers, media, communities, trends, monitors, webhooks, exports, etc. It includes 128 REST operations, 120 MCP routes (119 supporting JSON or text), OAuth 2.1 authentication. Not affiliated with X Corp.

Tools

explore

Browse the available route catalog of the MCP server to discover callable operations.

xquik

Execute X (Twitter) operations such as searching tweets, fetching user profiles, exporting followers, monitoring accounts, sending tweets, etc.

Setup

Obtain an Xquik API key: create one in the Xquik dashboard or through their platform.\n2. In your MCP client, configure a remote server with URL https://xquik.com/mcp.\n3. For OAuth-capable clients, use OAuth 2.1; otherwise, use the API key.\n4. Follow the client compatibility guide for configuration.

Fit and risk

Best for

Developers needing access to X data without a Twitter developer account.
Building social listening, market research, CRM, or monitoring tools.
Those needing multiple integration paths: REST, MCP, SDKs, webhooks.
Teams wanting confirmation-gated publishing to ensure safety.

Not for

Scenarios requiring full compliance with official Twitter API.
Scenarios requiring real-time streaming (Streaming API).
Accessing data or operations not supported by X Corp.
Organizations with strict security requirements for non-official services.

Required permissions

Read public X data (tweets, users, followers, etc.).
Perform write operations like posting, replying, liking, following, after user confirmation.
Create monitors, webhooks, export jobs, etc.
Requires Xquik API key or OAuth 2.1 authorization.
Certain operations require connected X account and explicit approval.

Risks and side effects

Non-official service may violate X's terms of service.
Third-party service may store or process data, consider privacy.
Write operations require caution and may affect your account.
Dependency on third-party service stability; may experience downtime.

Troubleshooting

If OAuth fails, check if client supports RFC 9207 iss parameter; e.g., for Codex, set XQUIK_API_KEY.
If connection fails, verify URL is correct and network is reachable.
If rate limited, note REST limits: GET 300 req/s, POST 120 req/min, DELETE 60 req/min.
If MCP route not supported, check version compatibility and refer to client compatibility guide.
If sending tweets fails, confirm account is connected and operation is confirmed.

Use cases

Search and fetch tweet data for market research or sentiment analysis.

Export follower lists for CRM or influencer analysis.

Monitor keywords or accounts and receive real-time alerts via webhooks.

Automate posting tweets, replies, likes, etc., with user confirmation.

Fetch trends, communities, Spaces, and other data.

Supported clients

Claude DesktopPartial support

Claude CodePartial support

OpenAI CodexPartial support

CursorPartial support

GitHub CopilotPartial support

Gemini CLIPartial support

WindsurfPartial support

ContinuePartial support

OpenHandsPartial support

Roo CodePartial support

Related MCP servers

Compare with other MCP servers