Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no X API key required.
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no X API key required. That is what the x mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
x-use drives a real, stealth-hardened browser instead of the paid X API. It posts, replies, searches, and engages across as many accounts as you configure, writes content with your own LLM, and exposes everything as MCP tools, so Claude Desktop, Claude Code, Cursor, and other MCP clients can run your X presence directly.
They are the same project. twitter-automation-ai was renamed to x-use for the v2 relaunch, which added the MCP server, the x-use CLI, draft mode, and the PyPI package. Old URLs still redirect, and stars, forks, and issues came across intact.
The server publishes 5 tools. What each one is for:
Group — ToolsMulti-account — Built-in: per-account config, cookies, proxiesProxies — Per-account proxies, named pools, hash/round-robin rotationStealth — undetected-chromedriver + selenium-stealth, randomized user agentsMetrics — Per-account counters + JSONL event logs, readable via MCPThe server ships on npm as skills, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: OPENAI_API_KEY, OPENAI_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. X's toolset — Group, Multi-account, Proxies and 2 more — is a fair guide to whether it matches your workflow. It is maintained by ihuzaifashoukat; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against X's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Group | Tools |
| Multi-account | Built-in: per-account config, cookies, proxies |
| Proxies | Per-account proxies, named pools, hash/round-robin rotation |
| Stealth | undetected-chromedriver + selenium-stealth, randomized user agents |
| Metrics | Per-account counters + JSONL event logs, readable via MCP |
{
"mcpServers": {
"x-use": {
"command": "npx",
"args": ["-y", "skills"],
"env": {
"OPENAI_API_KEY": "your-value",
"OPENAI_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| OPENAI_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.