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·

Claude Code Claude Desktop

HarnessClaude CodeClaude Desktop

Command center

Source

Review first

Review safety and privacy notes before installing or copying commands.

Safety notes Privacy notes

Install & copy

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}'

Trust & readiness

TrustReview first
Sourcesource-backed
Safety notesPresent
ReviewedYes

Community context

Related entries(4)
Related guides(3)
Community signals

Compare

Integrations & API

Contribute

Suggest a metadata change Claim this listing

Documentation Source repository Browse directory

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.

Canonical URL: https://heyclau.de/entry/mcp/xquik-mcp-server
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
Import PR: https://github.com/JSONbored/awesome-claude/pull/326
Claim status: unclaimed
Last verified: 2026-05-09

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context

Selected

Current score

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
Registry metadata indicates a reviewed listing.
Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Pending
Baseline comparison available
No baseline peer selected yet.
Pending
Diverging trust signals identified
No major trust-signal divergence found.
Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

3 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

4 to clear

Platforms

2 listed

Difficulty

0/100

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

Confirm source provenanceRequired
Source URL/provenance metadata is present.
Done
Confirm metadata review state
Listing has review metadata.
Done
Verify install payload
Install/config payload exists and can be inspected.
Done

Security checks

Confirm safety, privacy, and package integrity signals.

Review safety notesRequired
Safety notes are present.
Done
Review privacy notesRequired
Privacy notes are present.
Done
Verify package integrity metadata
No package verification/checksum metadata.
Pending

Rollout

Adopt in controlled steps based on the selected plan.

Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Pending
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Pending
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

4 prerequisites to line up before setup. Have accounts and credentials ready first.

0/4 ready

Account & credentials2Network & hosting23 minutes

Safety & privacy surface

1 safety and 1 privacy notes across 1 risk area. Review closely: credentials & tokens.

1 area

SafetyCredentials & tokensUse API keys with write confirmations enabled because posting, follower exports, media actions, and webhooks can affect public accounts.
PrivacyCredentials & tokensTimelines, profile data, follower exports, media, webhook details, and API credentials may be sent through model context.

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

Add the MCP configuration with your Xquik API key.
Restart your MCP client.
Ask Claude to explore available Xquik endpoints.
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.

#x #twitter #tweet-search #social-media #automation #webhooks #mcp-server

Source citations

Source methodology →

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](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.

2 trust signals differ across this comparison (Source provenance, Submitter).

Field	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. Open dossier	Mux MCP Server The official Mux MCP server (@mux/mcp) that gives AI agents access to the Mux API for video and analytics. It uses a "Code Mode" scheme — exposing a documentation-search tool and a code tool that runs agent-written TypeScript against the Mux SDK in an isolated sandbox — to work with Mux Video (assets, live streams, playback IDs, uploads) and Mux Data (viewer metrics and monitoring). Open dossier	Codacy MCP Server The official Codacy MCP server (@codacy/codacy-mcp) that gives AI assistants access to the Codacy API for code quality, security, and coverage — listing repository and pull-request issues, retrieving file coverage and duplication, searching security (SRM) findings, inspecting analysis tools and patterns, and running local analysis with the Codacy CLI. Open dossier	FastAPI-MCP Server FastAPI-native package that exposes FastAPI endpoints as Model Context Protocol tools while preserving schemas, docs, and existing authentication dependencies. Open dossier
Next steps	Open dossier API JSON Open LLM MCP feed Open source Newsletter Claim listing	Open dossier API JSON Open LLM MCP feed Open source Newsletter Claim listing	Open dossier API JSON Open LLM MCP feed Open source Newsletter Claim listing	Open dossier API JSON Open LLM MCP feed Open source Newsletter Claim listing
Trust
Review status	ReviewedMaintainer reviewed	ReviewedMaintainer reviewed	ReviewedMaintainer reviewed	ReviewedMaintainer reviewed
Package trust	Package not verified	Package not verified	Package not verified	Package not verified
Source provenanceDiffers	Submission linkedImport PR	Source-backed	Source-backed	Source-backed
SubmitterDiffers	kriptoburak	davion-knight	davion-knight	oktofeesh1
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Brand	Xquik	Mux MCP Server	Codacy MCP Server	FastAPI-MCP
Category	mcp	mcp	mcp	mcp
Source	source-backed	source-backed	source-backed	source-backed
Author	Xquik-dev	muxinc	codacy	Tadata
Added	2026-05-09	2026-07-08	2026-07-08	2026-06-05
Platforms	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Source repo	—	—	—	—
Safety notes	✓Use API keys with write confirmations enabled because posting, follower exports, media actions, and webhooks can affect public accounts.	✓This server uses a Code Mode scheme — the agent writes TypeScript against the Mux SDK and the server runs it in an isolated sandbox that has no web or filesystem access, then returns what the code prints or returns. The sandboxed code runs with your Mux access token, so it can create, modify, and delete real Mux resources (assets, live streams, playback IDs, uploads) within that token's permissions. Access is bounded by the Mux token's permissions, not by tool naming — scope the token to least privilege and prefer a non-production environment when an agent acts autonomously. Optional Mux signing and private keys enable signed playback URLs and JWTs; treat `MUX_SIGNING_KEY` and `MUX_PRIVATE_KEY` as secrets. Launching the client with the remote HTTP transport opens a network listener, so secure and authenticate it before exposing it beyond localhost.	✓The `codacy_cli_analyze` tool runs Codacy CLI analysis locally on files or directories, and if the CLI is not installed the server will attempt to download and install it, so it can execute and install software on your machine. The Codacy Account API Token grants API access to the organizations and repositories your account can see, including private ones, so treat it as a secret and scope it to least privilege. Most tools are read-only analysis (issues, coverage, duplication, security findings), but `codacy_setup_repository` adds or follows a repository in Codacy, which is an account-write action. Security (SRM) tools surface real vulnerabilities and findings for your code, so handle that output carefully and avoid leaking it. Prefer a token scoped to the intended organization and a non-sensitive repository when an agent acts autonomously.	✓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.
Privacy notes	✓Timelines, profile data, follower exports, media, webhook details, and API credentials may be sent through model context.	✓The server calls the Mux API with your credentials; asset metadata, live-stream details, and Mux Data results it returns are passed to the LLM/MCP client. Mux Data covers viewer and playback analytics (video views, errors, quality-of-experience metrics), which can include viewer and session information. Credentials (`MUX_TOKEN_ID`, `MUX_TOKEN_SECRET`, and any signing/webhook secrets) are provided via environment variables in your MCP client config — keep that config out of version control and restrict access to it. Video assets and analytics can reference real customer-facing content and usage, so avoid exposing a production account's data to the model unnecessarily.	✓The server calls the Codacy API with your token; repository metadata, code-quality issues, coverage, duplication, security findings, and pull-request data it returns are passed to the LLM/MCP client. Some tools return source-derived content — for example `codacy_get_pull_request_git_diff` returns a PR's Git diff and file-analysis tools return issue context — which can include real source code. Security findings can reveal sensitive vulnerability details about your codebase; review before sharing that output. The account token is provided via the `CODACY_ACCOUNT_TOKEN` environment variable in your MCP client config — keep that config out of version control and restrict access to it.	✓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.
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	Node.js and npm (the server runs via `npx -y @mux/mcp@latest`) A Mux account and an access token (token ID and secret) from the Mux dashboard Optional Mux signing/private keys or webhook secret if you use signed playback or webhook features An MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.)	Node.js and npm, with the `npx` command working (the server runs via `npx -y @codacy/codacy-mcp`) A Codacy account and an Account API Token from Codacy Account access management For local analysis, the Codacy CLI v2 (macOS/Linux/Windows via WSL); the server installs it if it is missing An MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.)	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.
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}'`	`npx -y @mux/mcp@latest`	`npx -y @codacy/codacy-mcp`	`uv add fastapi-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": { "mux": { "command": "npx", "args": ["-y", "@mux/mcp"], "env": { "MUX_TOKEN_ID": "your_token_id", "MUX_TOKEN_SECRET": "your_token_secret" } } } }`	`{ "mcpServers": { "codacy": { "command": "npx", "args": ["-y", "@codacy/codacy-mcp"], "env": { "CODACY_ACCOUNT_TOKEN": "<YOUR_TOKEN>" } } } }`	`{ "mcpServers": { "fastapi-mcp": { "url": "http://localhost:8000/mcp", "type": "http" } } }`
Citations	Source repositorygithub.com 2026-07-13T15:19:32-07:00 Documentationdocs.xquik.com Submitted by kriptoburak2026-05-09 Source methodology →	Source repositorygithub.com 2026-07-13T15:19:32-07:00 Documentationgithub.com Submitted by davion-knight2026-07-08 Source methodology →	Source repositorygithub.com 2026-07-13T15:19:32-07:00 Documentationgithub.com Submitted by davion-knight2026-07-08 Source methodology →	Source repositorygithub.com 2026-07-13T15:19:32-07:00 Documentationfastapi-mcp.tadata.com Submitted by oktofeesh12026-06-05 Source methodology →
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed