X Use

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. Server-side LLM functions are optional; the README does not specify which LLM providers or environment variable names they require.

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