Skip to main content
hc
Submit
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·added 2026-05-09·87 source repo stars·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

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
Stars
87 source repo stars
Forks
8
Updated
2026-05-18T21:56:17Z
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 and logs, and connect an X account only when you need write workflows.

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.
Content outline
#x#twitter#tweet-search#social-media#automation#webhooks#mcp-server

Source citations

Signals

Loading live community signals…

More like this, weekly

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