M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
X

Xquik MCP

Community
MCP server for X (Twitter) data extraction and publishing automation
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #243 of 438
Stars
★ 212 Very popular
Transport
Streamable HTTP
Runtime
Hosted (no local runtime)
Credentials
API key / credential required
License
MIT
Last commit
Tools
2
51FMRS · D

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.

Strongest · Documentation 15/20 Weakest · Reliability 4/20

Reliability
4/20
Security and permissions
8/20
Maintenance
11/20
Documentation
15/20
Setup experience
13/20
Why each score
Reliability 4/20
Evidence: server.json declares a remote streamable-http endpoint and 120 MCP routes through 2 tools; README claims 119 JSON/text routes and 128 REST operations. Deductions: only manifest and README supplied; no source code, CI workflow, or test files prove the handshake or behavior; tool list vs implementation cannot be verified; dependencies/error handling uncontrollable. Under static calibration cannot exceed 12, so 4.
Security and permissions 8/20
Evidence: README documents OAuth 2.1, XQUIK_API_KEY, no X passwords/2FA/cookies, scoped access, confirmation-gated writes, HMAC webhooks, and boundary handling of untrusted X content. No red-line issues found (no malware, no real-token install examples, no default destructive operations). Deductions: these are claims without reviewable implementation; credential storage, least-privilege enforcement, and confirmation flow cannot be confirmed; API-key fallback varies by client and the Codex OAuth issuer issue shows compatibility risk.
Maintenance 11/20
Evidence: repo not archived, 3 open issues, MIT license, README links to org support/security/contribution policies, version 2.6.1, and unverified CI/CodeQL/OpenSSF badges. Deductions: no commit history, release cadence, issue response times, or dependency update records supplied; badges are README claims; stars are only a discovery signal.
Documentation 15/20
Evidence: README includes install commands, manual installation steps, agent target directories, API route tables, rate limits, safety rules, SDK list, references/FAQs, client compatibility and troubleshooting links—layered and detailed. Deductions: tool parameters, concrete client config examples, and cost specifics live in external docs not supplied; exact alignment with implemented endpoints cannot be checked.
Setup experience 13/20
Evidence: remote MCP setup reduces to adding https://xquik.com/mcp in a client, with OAuth 2.1 or API key; skill install provides npx and manual copy steps with target directories for many agents. Deductions: no ready-to-paste client config examples in the supplied material; auth fallback and Codex-specific handling rely on external guides; static cap 15 and no execution verification.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

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.

Setup

Before you start

Runtime：Hosted (no local runtime)

XQUIK_API_KEY requiredsecret Xquik API key used for public reads and API-key fallback auth (e.g., Codex OAuth compatibility); create it in the Xquik dashboard under API Keys.
  1. 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.

Check that it works

After connecting the client to https://xquik.com/mcp, the tool list should show the two tools explore and xquik; calling explore should return the 120-route catalog.

Troubleshooting

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

Things to try

Once connected, you can ask your AI assistant things like:

  • Search recent tweets about Model Context Protocol and show engagement metrics
  • Export the follower list of @xquik and estimate usage first
  • Monitor an account for new tweets and notify me via webhook
  • Run a giveaway draw from a tweet's replies and pick winners

Tools 2

explore read-only
Browse the available route catalog of the MCP server to discover callable operations.
xquik read-only
Execute X (Twitter) operations such as searching tweets, fetching user profiles, exporting followers, monitoring accounts, sending tweets, etc.

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
CodexPartial support
CursorPartial support
GitHub CopilotPartial support
Gemini CLIPartial support
WindsurfPartial support
ContinuePartial support
OpenHandsPartial support
Roo CodePartial support

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 588529e8f231 Data synced 2026-10-12 Read the FMRS scoring method