Xee-mcp — MCP server for X (Twitter): search + read, no paid API

What is Xee-mcp? It's a Model Context Protocol server that gives Claude, ChatGPT, and other AI assistants two read-only tools for X (Twitter): search posts and read a user's timeline. It uses cookie-based auth via twikit — no X API keys, no pay-per-use fees.

Naming: X + See = Xee (pronounced "ex-ee"). The name encodes the scope — Xee-mcp is for seeing X, not posting to it. Posting is intentionally out-of-scope for v0.x.

Status (v0.1.0)

xee-mcp init (cookie setup) works. search and user_tweets are temporarily degraded — they return a clear "upstream parser broken" error because twikit (the underlying scrape library) can't parse X's current webpack chunk format to build the X-Client-Transaction-Id header. This is not a cookie problem — your auth is fine.

This is upstream's repo to fix; we don't fork or maintain a patched scraper. When twikit ships a parser fix, bump the dep and these tools resume working with no code change on your side. See docs/upstream-issues.md for the technical details.

Why ship now anyway: the setup UX (xee-mcp init) is the value users feel first. Shipping that lets people install, configure, and be ready — so the day upstream lands a fix, the tools just start working.

Why Xee-mcp

Six MCP servers for X already exist. Most require the paid X API — pay-per-use since Feb 2026, ~$0.005 per read. For solo developers and OSS authors who just want to let Claude search what's being said about their work, that's wrong shape.

Xee-mcp solves one job: read X with zero API cost. Cookie auth via twikit, two tools, one MCP server. That's it.

If you want posting, DMs, or production-grade reliability — use one of the others. If you want the smallest thing that lets Claude see X for you, use Xee-mcp.

Tools

search(query, limit=20)

Search X posts by keyword. Returns text, author, timestamp, URL, and engagement stats.

user_tweets(handle, limit=20)

Read a user's recent posts. Returns the same fields.

That's the v0.1 surface. Two tools. Read-only. No surprises.

Install

git clone https://github.com/Aiyo28/Xee-mcp.git
cd Xee-mcp
uv sync

PyPI publish follows the first wave of feedback (pip install xee-mcp).

Quickstart

1. Log in to x.com in Chrome (or Brave / Arc / Firefox / Safari / Edge — any one).

2. One-shot cookie setup. Reads your existing browser session — no extension, no DevTools paste, no password:

   uv run xee-mcp init
   export XEE_MCP_COOKIES=~/.config/xee-mcp/cookies.json

   On macOS Chrome / Brave / Edge you'll see one Keychain prompt — approve it. For other browsers use --browser brave|arc|firefox|safari|edge. Other setup paths (advanced / headless) are in docs/cookies.md.

3. Wire into Claude Desktop / Claude Code. Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

   {
     "mcpServers": {
       "xee-mcp": {
         "command": "uv",
         "args": ["run", "--directory", "/path/to/Xee-mcp", "xee-mcp"],
         "env": { "XEE_MCP_COOKIES": "/path/to/cookies.json" }
       }
     }
   }

4. Ask Claude:

   "Search X for posts about MCP servers from the last week." "Show me the last 10 posts from @simonw."

Limitations

• Single account. v0.1 uses one cookie file. If X bot-detects, you wait it out or rotate. Multi-account pool is roadmapped (see twscrape swap path in ROADMAP.md).

• Read-only. No post, no DMs, no like/retweet. Intentional — see naming.

• No analytics dashboard. This is a primitive, not a product. Compose with other MCP tools.

• Cookie auth is brittle by design. X may rotate session formats. Pin issues here.

Roadmap

See ROADMAP.md. v0.2 likely adds replies + bookmarks (still read). Posting stays separate (different threat model, different repo).

Support the project

Xee-mcp is MIT, ad-free, and will never have paid tiers. If it saves you time or money, you can throw a coffee:

paypal.me/aiyo28 — keeps everything ad-free, no paid tiers, ever.

Or just star the repo and tell someone. That works too.

Related projects

• Yzel — MCP connectors for CIS business tools (1C, Wildberries, Ozon, Bitrix24, AmoCRM, МойСклад, Telegram, iiko). Sibling OSS project, different scope (CIS-first business APIs).

License

MIT. See LICENSE.