X Use logo

X Use

by ihuzaifashoukat

Automates multiple X accounts through Chrome and MCP, with cookie login, draft approval, search, engagement, and queued actions.

Install X Use

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ihuzaifashoukat-x-use": {
      "command": "uvx",
      "args": [
        "--from",
        "x-use-mcp==3.0.0",
        "x-use"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx --from x-use-mcp==3.0.0 x-use

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

ihuzaifashoukat/x-use MCP server automates X accounts through a real Chrome session authenticated with your own cookies, without requiring an X API key. It exposes 33 MCP tools for reading tweets, searching, posting, replying, engagement, account management, proxies, and queued actions. Write operations produce drafts by default, and nothing is published until an approval tool is called. Reach for it when an MCP client needs browser-based, multi-account X workflows with optional personas and server-side LLM features.

Use cases

  • Automate posting across multiple X accounts
  • Search X keywords and prepare replies for review
  • Review tweet images before drafting responses
  • Queue posts and engagement actions for explicit processing
  • Manage account personas and browser proxies

Key features

  • Browser-based X automation with Chrome cookies
  • 33 MCP tools over stdio
  • Multi-account management and personas
  • Draft approval for write actions
  • Persistent scheduled-action queue
  • Proxy pool management

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

13/13 checks healthy over the last 92d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · x-use (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars181Stargazers on the source repository.
Last commit6d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How X Use works

What ihuzaifashoukat/x-use MCP server does

ihuzaifashoukat/x-use MCP server gives MCP clients access to X account operations through a browser rather than the X API. It uses Chrome and imported account cookies, so an X API key is not required. The server can work with multiple configured accounts and supports account-specific personas, proxy pools, metrics, searches, tweet reads, replies, posting, and engagement actions.

The package exposes 33 tools across read-only operations, draft-gated writes, scheduled queue management, composite LLM workflows, account management, and proxy management. A tweet read can return images as MCP content, allowing a client to inspect visual content before preparing a response.

How it works

The MCP server runs locally over stdio with the x-use mcp command. An MCP client such as Claude Desktop, Cursor, or Windsurf connects to that process and calls the exposed tools. Browser sessions are created for configured accounts as needed, and account data, drafts, and queued actions are stored locally.

Write tools use a review gate by default. Calls such as posting, replying, or engagement return a draft rather than immediately changing X. The client or operator must call approve_draft with the returned draft ID before publication. Draft mode can be disabled in config/settings.json with the documented MCP setting.

The queue provides another explicit execution boundary. Queued posts and engagement actions remain stored until process_queue is called. Persistent JSONL files retain drafts and queue entries across restarts. Optional server-side LLM configuration supports composite tools, automatic text, and background automation; interactive use can instead supply explicit text from the MCP client without an LLM key.

Setup and configuration

Install the PyPI package with pip install x-use-mcp. The project requires Python 3.10 or newer and Chrome. Run x-use init for the interactive setup wizard, including presets, account and cookie import, and LLM configuration. Run x-use doctor to check the browser or driver, cookies, LLM keys, and proxies.

After setup, register the local server in an MCP client using the command x-use with the argument mcp. If the executable is not on the client PATH, use the full path printed by the installer. Restart the client and ask it to call list_accounts to verify the connection.

Account configuration, keywords, personas, and optional proxies are managed through the project setup flow and its configuration files. The repository also documents client registration for Claude Desktop, Claude Code, Codex, Cursor, and Windsurf.

Tools and capabilities

The tool groups include:

  • Read account details, health, metrics, drafts, queue entries, run status, proxies, tweets, and search results.
  • Create and approve drafts for posts, generated posts, replies, engagement, and automation cycles.
  • Queue posts or engagement actions, cancel queued work, and process the queue explicitly.
  • Run composite research and content-variation workflows that can use the server-side LLM.
  • Add, update, activate, or remove accounts.
  • Add, remove, and test proxies.

The server also provides MCP prompts for niche research, reply drafting, review and publishing, daily checks, and account setup. Read-only resources expose masked account data, personas, and pending drafts without sending secrets through the resource contents.

Limitations and notes

Browser automation depends on a working Chrome installation and valid imported cookies. The server does not use the X API, but browser access still depends on the configured accounts remaining usable in Chrome.

Draft approval is enabled by default, so write calls alone do not publish content. Likewise, adding an action to the queue does not execute it until process_queue is called. The project is licensed under MIT and supports Python 3.10+.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about X Use

Install the PyPI package with `pip install x-use-mcp`, then run `x-use init` to configure it.

Yes. Register `x-use` as the command and `mcp` as its argument in Claude Desktop's MCP configuration, then restart the client.

No. It drives a real Chrome session using imported account cookies instead of the X API.

Draft mode is enabled by default. Write tools return a draft, and publication requires calling `approve_draft` with its draft ID.

It requires Python 3.10 or newer, Chrome, and configured X account cookies. An LLM key is optional for server-side LLM features.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewX Use AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ihuzaifashoukat-x-use?style=directory)](https://allmcps.com/mcp/ihuzaifashoukat-x-use)
HTML Embed
<a href="https://allmcps.com/mcp/ihuzaifashoukat-x-use"><img src="https://allmcps.com/api/badge/ihuzaifashoukat-x-use?style=directory" alt="X Use on AllMCPs" /></a>