# The X (Twitter) MCP server that posts what you approve

> Liftli is a remote X (Twitter) MCP server. Add one URL to Claude, ChatGPT or Grok to publish and schedule X posts and threads via X's official API.
>
> Markdown version of https://liftli.ai/x-mcp. Updated 2026-10-14.

Liftli is a remote **X MCP server**. Paste one URL into Claude, ChatGPT, Codex or Grok, connect your X account on X's own sign-in page, and your AI can plan, write, publish and schedule X posts and threads in your own voice. Everything goes through X's official API, and nothing posts until you approve it.

- [Start free, no card](https://app.liftli.ai/console/login?intent=signup)
- Get the MCP URL

Maintained by [Oded Tsamir](https://www.linkedin.com/in/odedtsamir/), founder of Liftli · last reviewed October 2026

## What an X MCP server does

An X MCP server is a connector that lets an AI assistant work with X through the Model Context Protocol (MCP). It is what people mean when they search for "Claude Twitter" or "Claude for Twitter": you tell Claude "post this thread tomorrow at 9" and it happens, after you say yes, instead of you copying a draft out of a chat window.

Most X MCP servers on GitHub are thin wrappers around the X API that you run with your own developer keys, or data tools for reading X. Liftli is built to help you **show up** on X: decide what to say, write it the way you write, and post it at the right time.

## Connect it in a minute

One remote MCP URL works in every client. There is nothing to install, clone or run locally:

```
https://mcp.liftli.ai/mcp
```

| Client | How to add the X MCP |
|---|---|
| Claude (web, desktop, mobile) | Customize (briefcase icon) → Connectors → Add custom connector → paste `https://mcp.liftli.ai/mcp` |
| Claude Code | `claude mcp add --scope user --transport http liftli https://mcp.liftli.ai/mcp` |
| ChatGPT (custom app) | On a computer: Plugins → Add → Create MCP App (or + → Create app) → add the same URL. If there is no create option or ChatGPT asks for Developer mode, turn it on under Settings → Security and login |
| Codex, Cursor (beta) | Add a remote MCP server pointing at the same URL |
| Grok (grok.com) | grok.com/connectors → New Connector → Custom → the same URL |

Then say "connect my X account". Liftli sends you to X's own sign-in page (OAuth 2.0 with PKCE); you approve there, and X gives Liftli permission to post for you. Liftli never sees your X password. Full setup for every client is on the [developers page](https://liftli.ai/developers).

## What your AI can do on X with Liftli

- **Publish and schedule posts and threads.** "Post this now" or "schedule the thread for Tuesday at 9". A thread publishes in order, as one conversation.
- **Write for X, not for LinkedIn.** Short posts of up to 280 characters, threads where post 1 stands alone, and long posts of up to 25,000 characters if you have X Premium ([X's limit](https://help.x.com/en/using-x/x-premium-how-to)).
- **Write in your voice.** Liftli learns your voice from your own posts, so drafts sound like you and not like a reply bot.
- **Pressure-test every draft.** Each post is critiqued for the things X rewards: a hook that works cold and a real reason to reply. Bait gets cut.
- **Draft replies you post yourself.** Short, specific replies to other people's posts. Liftli never posts a reply for you.
- **Turn real work into posts.** Voice notes, call transcripts, GitHub activity and the news become post ideas grounded in what actually happened.
- **One plan across networks.** The same strategist covers LinkedIn and X, and drafts Substack issues and Notes (Liftli does not publish to Substack).

It remembers your strategy, voice and results between sessions and across clients. See [Liftli for X](https://liftli.ai/x) for how it plans the conversation, not just the broadcast.

## X and Twitter MCP servers on GitHub, compared

Checked on 14 October 2026. Each is good at a different job.

| Server | What it does | How it reaches X | Setup |
|---|---|---|---|
| Liftli | Plans, writes, critiques, publishes and schedules your posts and threads, in your voice | X's official API, connected with X's sign-in | Paste one URL. X publishing is on the Business plan |
| [xdevplatform/xmcp](https://github.com/xdevplatform/xmcp) | Exposes the X API's endpoints as MCP tools: posts, search, DMs, lists, bookmarks and more, with an allowlist to load only some. From X's developer platform GitHub organization | X's official API, with keys from your own X developer app | Run a local Python server; remote clients need a tunnel |
| [EnesCinr/twitter-mcp](https://github.com/EnesCinr/twitter-mcp) | Two tools: post a tweet and search tweets | X's official API, with your own developer keys | An npx package in your client's config |
| [Infatoshi/x-mcp](https://github.com/Infatoshi/x-mcp) | Post, quote, delete, search, read timelines and mentions, upload media, read post metrics | X's official API, with five credentials from your developer app | Clone, build and run it locally |
| [6551Team/opentwitter-mcp](https://github.com/6551Team/opentwitter-mcp) | Reads X data: profiles, tweet search, follower events, KOL tracking. No posting | A third-party data API, with a token from its provider | A local server you run |
| [adhikasp/mcp-twikit](https://github.com/adhikasp/mcp-twikit) | Searches and reads tweets | The twikit library, which describes itself as a scraper of X's internal API, signed in with your X username, email and password | uvx or Smithery |

If you want raw access to the X API for research or your own bots, xmcp from X's developer platform is the most complete. If you want to post consistently in your own voice without running a server or holding API keys, that is what Liftli is for. Whatever you pick, check how it reaches X: X's [automation rules](https://help.x.com/en/rules-and-policies/x-automation) forbid non-API automation such as scripting the X website.

## Using an X agent skill? Add the MCP to post

Agent skills are instructions your AI runs locally. They can help it write a better X post, but a skill cannot publish on its own. Liftli ships both: 11 free [X agent skills](https://liftli.ai/x-agent-skills/) you can install with `npx skills add liftli-ai/x-agent-skills`, and the MCP server that takes the finished post and publishes or schedules it.

## Safe for your X account

- **Official API only.** No browser extension, no scripted clicks on x.com, no bot actions on your profile.
- **You approve every post.** Nothing is published or scheduled without your explicit go-ahead.
- **No automated replies.** Liftli drafts replies; you post them. X requires its prior written approval for AI reply bots.
- **You stay in control.** You can remove Liftli's access at any time from the connected apps in your X settings.

Details on what Liftli can access and store are on the [security page](https://liftli.ai/security).

## Pricing

Publishing and scheduling to X are on the Business plan: $79 a month, or $790 a year, with a fair-use cap of 100 posts a month. Business covers LinkedIn, X and Substack drafting under one strategist. Start free with no card to try the strategist and publish to LinkedIn; Pro is $29 a month at the founding rate for LinkedIn. Liftli adds no AI markup, because it runs inside the AI subscription you already pay for. [See all plans](https://liftli.ai/pricing).

## Frequently asked questions

**What is an X (Twitter) MCP server?**

An X MCP server is a connector that lets an AI assistant such as Claude or ChatGPT work with X through the Model Context Protocol. Once it is connected, you can ask the assistant to draft, publish or schedule X posts and threads in plain language instead of copying text into X yourself.

**Can Claude post to Twitter?**

Yes, through an MCP server that uses X's official API. With Liftli connected, you ask Claude to post or schedule a post or thread, approve it, and Liftli publishes it through X's official API. Claude on its own, or with skills only, cannot post.

**Which AI clients does the Liftli X MCP work with?**

Claude (web, desktop and mobile), ChatGPT (as a custom app), Claude Code, Codex, Cowork, Grok and Grok Bot today, with Cursor, Hermes, OpenClaw and other MCP clients in beta. Every client uses the same URL: https://mcp.liftli.ai/mcp.

**Will an X MCP server get my account suspended?**

It depends on how the server reaches X. X's automation rules forbid non-API automation, such as scripting the X website, and AI reply bots need X's prior written approval. Liftli publishes only through X's official API, only the posts you approve, and never posts replies for you.

**Do I need an X developer account or API keys?**

No. Liftli runs its own app on X's official API. You connect your account on X's own sign-in page, and Liftli never sees your X password. Self-hosted servers such as xmcp need your own X developer app and keys.

**Can Liftli write long posts and threads?**

Yes. It writes standard posts of up to 280 characters, threads that publish in order, and long posts of up to 25,000 characters if your account has X Premium, which is X's own limit for longer posts.

**Does Liftli reply to people on X for me?**

No. Liftli drafts replies when you ask, and you post them yourself. X's automation rules restrict automated replies, and a reply that reads like a bot gets ignored or muted.

**How much does the Liftli X MCP cost?**

Publishing and scheduling to X are on the Business plan, $79 a month or $790 a year, with a fair-use cap of 100 posts a month. You can start free with no card to try the strategist and publish to LinkedIn. Pro is $29 a month at the founding rate and covers LinkedIn.