Skip to main content
mcpSource-backedReview first Safety Privacy

Xquik MCP Server

Remote MCP server for X and Twitter automation: tweet search, profile timelines, follower export, media workflows, webhooks, and confirmation-gated write actions.

by Xquik-dev · submitted by kriptoburak·added 2026-05-09·
HarnessClaude CodeClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://docs.xquik.com/mcp/overview, https://github.com/Xquik-dev/x-twitter-scraper
Brand
Xquik
Brand domain
xquik.com
Brand asset source
manual
Safety notes
Use API keys with write confirmations enabled because posting, follower exports, media actions, and webhooks can affect public accounts.
Privacy notes
Timelines, profile data, follower exports, media, webhook details, and API credentials may be sent through model context.
Author
Xquik-dev
Submitted by
kriptoburak
Claim status
unclaimed
Last verified
2026-05-09

Safety notes

  • Use API keys with write confirmations enabled because posting, follower exports, media actions, and webhooks can affect public accounts.

Privacy notes

  • Timelines, profile data, follower exports, media, webhook details, and API credentials may be sent through model context.

Prerequisites

  • Xquik account and API key from https://dashboard.xquik.com/account
  • Connected X account before using write actions such as posts, DMs, profile updates, or follows
  • MCP client with stdio support through mcp-remote or direct Streamable HTTP support
  • Network access to https://xquik.com/mcp

Schema details

Install type
cli
Reading time
3 min
Difficulty score
0
Troubleshooting
Yes
Breaking changes
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
3 minutes
Difficulty
beginner
Full copyable content
{
  "mcpServers": {
    "xquik": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.1.38",
        "https://xquik.com/mcp",
        "--header",
        "x-api-key:${XQUIK_API_KEY}"
      ],
      "env": {
        "XQUIK_API_KEY": "xq_YOUR_KEY_HERE"
      }
    }
  }
}

About this resource

Overview

Xquik MCP Server connects Claude and other MCP clients to Xquik's X and Twitter automation platform. Agents can search tweets, fetch profile timelines, export followers, retrieve media metadata, manage monitors, configure webhooks, and run confirmation-gated X write workflows through a remote MCP endpoint.

The server exposes explore for searching the API catalog and xquik for authenticated API calls. This makes it useful for social listening workflows, analytics pipelines, media collection, campaign monitoring, and controlled write flows that need human confirmation before account actions.

Usage

export XQUIK_API_KEY=xq_YOUR_KEY_HERE
npx -y mcp-remote@0.1.38 https://xquik.com/mcp --header 'x-api-key:${XQUIK_API_KEY}'

Auth Requirements

Xquik supports API-key authentication through the x-api-key header and OAuth 2.1 for clients that support browser-based MCP connectors. Create an API key from the Xquik dashboard, keep it out of prompts, logs, and shell-expanded command arguments, and connect an X account only when you need write workflows. The mcp-remote command examples quote the header placeholder with single quotes so the client can resolve XQUIK_API_KEY from the environment without placing the expanded secret in shell argv.

Capabilities

  • Search tweets with keywords and advanced query filters.
  • Fetch user profiles, profile timelines, followers, and following data.
  • Retrieve media metadata and downloadable media URLs.
  • Create monitors and HMAC-signed webhook delivery workflows.
  • Run confirmation-gated write workflows for connected X accounts, including posts, replies, DMs, follows, profile updates, and media actions.

Verification

  1. Add the MCP configuration with your Xquik API key.
  2. Restart your MCP client.
  3. Ask Claude to explore available Xquik endpoints.
  4. Run a read-only tweet or profile lookup before using write workflows.

Security Notes

  • Keep XQUIK_API_KEY out of prompts, logs, and shared configuration files.
  • Review the exact payload before any post, reply, DM, follow, profile update, media upload, or billing/top-up workflow.
  • Prefer read-only exploration first, then authorize write actions only when needed.
  • Treat webhooks and monitors as ongoing external delivery workflows; verify destination URLs and HMAC signature handling before enabling them.

Source citations

Add this badge to your README

Show that Xquik MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/xquik-mcp-server.svg)](https://heyclau.de/entry/mcp/xquik-mcp-server)

How it compares

Xquik MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Remote MCP server for X and Twitter automation: tweet search, profile timelines, follower export, media workflows, webhooks, and confirmation-gated write actions.

Open dossier

FastAPI-native package that exposes FastAPI endpoints as Model Context Protocol tools while preserving schemas, docs, and existing authentication dependencies.

Open dossier

Search the public HeyClaude registry, fetch entry details, inspect compatibility, and build PR-first submission URLs through MCP.

Open dossier

Memesio MCP Server is a hosted MCP endpoint for meme template discovery, captioned meme creation, share links, and AI-assisted meme generation. Public tools support anonymous/rate-limited usage, while optional developer or agent keys unlock higher-rate, premium, and AI-powered actions.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandXquikFastAPI-MCP logoFastAPI-MCPHeyClaude logoHeyClaudeMemesio logoMemesio
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorXquik-devTadataHeyClaude TeamMemesio
Added2026-05-092026-06-052025-11-252026-05-08
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesUse API keys with write confirmations enabled because posting, follower exports, media actions, and webhooks can affect public accounts.FastAPI-MCP can expose real API operations as tools; do not blindly expose admin, destructive, payment, credential, or production-write endpoints. Preserve and test FastAPI authentication dependencies before letting agents call protected tools. Review request models, side effects, rate limits, and authorization boundaries for each endpoint. Prefer explicit allowlists and non-production deployments for early MCP testing.Runs the public HeyClaude MCP endpoint through mcp-remote when installed through stdio clients. Exposes read-only registry and draft-validation tools; it does not publish content, open PRs, or mutate GitHub.Review generated memes and share links before publishing, and avoid uploading sensitive images or private text.
Privacy notesTimelines, profile data, follower exports, media, webhook details, and API credentials may be sent through model context.Request schemas, response schemas, OpenAPI docs, route names, validation errors, and endpoint outputs may be visible to the MCP client and model. Endpoint calls can expose user data, internal identifiers, tokens in payloads, and business logic. Keep API credentials, service secrets, and test-user tokens out of prompts, repository files, and logs.MCP queries and draft metadata are sent to the HeyClaude MCP endpoint when used through a remote client. Do not include credentials, private repository details, customer data, or unpublished material in draft fields.Prompts, source images, captions, API keys, generated outputs, and shared asset URLs may be sent through the integration.
Prerequisites
  • Xquik account and API key from https://dashboard.xquik.com/account
  • Connected X account before using write actions such as posts, DMs, profile updates, or follows
  • MCP client with stdio support through mcp-remote or direct Streamable HTTP support
  • Network access to https://xquik.com/mcp
  • Python 3.10 or newer, with Python 3.12 recommended by the project.
  • Existing FastAPI application or a reviewed FastAPI service design.
  • uv or pip for installing fastapi-mcp.
  • Clear endpoint allowlist and authentication policy before exposing API operations to an agent.
  • MCP client with Streamable HTTP support, or stdio support via mcp-remote
  • Network access to https://heyclau.de/api/mcp
  • Optional local checkout if running the stdio package directly from the repo
— none listed
Install
XQUIK_API_KEY=xq_YOUR_KEY_HERE npx -y mcp-remote@0.1.38 https://xquik.com/mcp --header 'x-api-key:${XQUIK_API_KEY}'
uv add fastapi-mcp
npx -y mcp-remote https://heyclau.de/api/mcp
claude mcp add --transport http memesio https://memesio.com/api/mcp
Config
Manual-only setup:
{
  "mcpServers": {
    "xquik": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.1.38",
        "https://xquik.com/mcp",
        "--header",
        "x-api-key:${XQUIK_API_KEY}"
      ],
      "env": {
        "XQUIK_API_KEY": "xq_YOUR_KEY_HERE"
      }
    }
  }
}
{
  "mcpServers": {
    "fastapi-mcp": {
      "url": "http://localhost:8000/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "heyclaude": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://heyclau.de/api/mcp"]
    }
  }
}
{
  "mcpServers": {
    "memesio": {
      "type": "http",
      "url": "https://memesio.com/api/mcp"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.