MCP server, by Xquik
Xquik MCP Server
Hosted MCP server for Xquik that lets an AI client search X (Twitter) posts, export followers and replies, retrieve profiles, and run account monitors through the Xquik API.
Quick facts
What it does
Xquik is an independent third-party X (Twitter) data service, not affiliated with X Corp. Its hosted MCP server exposes the Xquik REST API to AI clients over Streamable HTTP at https://xquik.com/mcp, and the same data is also available through REST, SDKs, and a CLI. The official MCP documentation is the setup and feature source for this record; the Xquik team submitted the server for this catalog. Xquik has paid subscription plans and usage-based pay-as-you-go billing.
Per the official documentation, the MCP server defaults to Code Mode with three tools: docs searches the public Xquik documentation, search searches the API specification, and execute runs API requests in a sandbox. Through those operations a client can search tweets, export followers, following lists, and replies, retrieve profiles, analyze post sentiment, and create account or keyword monitors that deliver signed webhook events. Billing is per delivered result for scraping operations: the official site states that most tweet, profile, and follower reads cost 1 credit per result, and that Xquik charges only for delivered, unique, filter-matching results. Protected, deleted, or otherwise unavailable X content may not be accessible.
Configuration
Add an MCP server named Xquik with Streamable HTTP transport and url https://xquik.com/mcp, then complete the OAuth 2.1 browser sign-in and consent flow when the client prompts. Clients without OAuth support can instead send an Xquik API key created in the Xquik dashboard, as an x-api-key header or an Authorization Bearer token, where the client supports secure header storage. No npm server package is needed; the tools run on the Xquik server. A separate Docs MCP server is offered at https://docs.xquik.com/mcp for public documentation search.
{"mcpServers":{"xquik":{"type":"http","url":"https://xquik.com/mcp"}}}Source: https://docs.xquik.com/mcp/overview. Placeholders only. Replace them in your own environment, and never commit real keys to a repository.
| Environment variable | Required | Purpose |
|---|---|---|
XQUIK_API_KEY | Optional | Xquik account API key, used only as the fallback authentication method for clients that cannot complete the OAuth 2.1 flow. |
Tools and features on record
docs Config checked
Searches the public Xquik documentation from inside the MCP session. Read-only.
search Config checked
Searches the Xquik API specification so the client can discover available operations before calling them. Read-only and uses no credits; MCP authentication is still required.
execute Config checked
Runs Xquik API requests in a sandbox, covering tweet search, follower and reply exports, and profile retrieval; with full credentials it can also run write operations such as posting, which spend credits.
Monitors and webhooks Config checked
Account and keyword monitors check for new matching X activity and deliver events to a registered HTTPS webhook; webhook deliveries are HMAC-SHA256 signed.
Sentiment analysis Config checked
Analyzes post sentiment and related signals such as brand mentions through the same API surface.
Security notes
- Authentication is OAuth 2.1 (recommended, discovered from the endpoint) or an Xquik API key sent as an x-api-key header or Bearer token; unauthenticated requests receive a 401 challenge. Full account keys expose every catalog route, while guest keys are limited to eligible paid-read routes.
- The MCP boundary excludes money movement: API key management, subscriptions and top-up checkout, and guest wallet operations stay outside MCP and run through the dashboard or direct REST only.
- Xquik is an independent third-party service and is not affiliated with X Corp. It reads X content that is visible without signing in; protected, deleted, or restricted content may stay inaccessible.
An MCP server runs with the permissions of the process you start it from. Scope credentials to the narrowest access the job needs, and review what the client will send before connecting anything sensitive.
Sources and freshness
- Official source: https://docs.xquik.com/mcp/overview
- Repository: https://github.com/Xquik-dev/x-twitter-scraper
Checked 2026-10-29. Config-checked means the configuration and feature list trace to the official source above; it does not mean AgentsUse ran the server. Send corrections through the contact page. Back to the MCP server index.