Submit
MCP Servers2026-05-09

Xquik / xquik.com

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.

xtwittertweet-searchsocial-mediaautomationwebhooksmcp-server
Raycastdocssourcebrand
External sourceInstall pathCopy-readyAttributed
Edit on GitHubSuggest change

Author

Xquik-dev

Added

2026-05-09

Setup time

3 minutes

Difficulty

beginner

Quick use

Install command

1 lines
npx -y mcp-remote@0.1.38 https://xquik.com/mcp --header "x-api-key:${XQUIK_API_KEY}"

Claude config

.claude/settings.json

17 lines
{
  "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"
      }
    }
  }
}

Source asset

bash

2 lines
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}"

Section

Overview

Expand

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.

Section

Auth Requirements

Expand

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.

Section

Capabilities

Expand
  • 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.

Section

Verification

Expand
  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.

Section

Security Notes

Expand
  • 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.

0% complete