How to give Claude your X post performance data

To give Claude your X post performance data, you need a source it can read on every draft: an exported archive you paste in, X's own MCP server with your developer credentials, or an MCP server that already stores your measured posts. LinkIntel is the third kind. Once you connect X, it reads your recent original posts and their metrics every day and serves them to Claude as a cited content brief, alongside X's published ranking weights. It never posts and never searches X on its own.

Three ways to get your X results into Claude

You can paste an export into a chat, connect Claude to X's official MCP server, or connect Claude to an MCP server that keeps its own snapshots of your posts. The first costs nothing but is manual. The second gives live access to the X API but needs your own developer app. The third needs a subscription but keeps a history your assistant can read on every draft without you doing anything.

Option 1: paste or export your posts (X data archive)

X lets you download an archive of your data, and the archive holds your posts as files you can hand to an assistant. On the web you open More, then Settings and privacy, then Your account, then Download an archive of your data, confirm your password and request the archive. X's help page on accessing your X data says the archive is usually ready within about 24 hours, and the download link is time-limited (commonly reported as 7 days).

The archive includes the text of every post, reply and repost with its post ID. It is a good record of what you wrote. What it does not give you is a full performance record: it carries like and repost counts, but impressions and detailed engagement live in X's separate analytics dashboard, and that is where you would export a CSV from if you have access to it. So with this route you usually end up pasting two things together, or telling Claude only what you wrote and not how it did.

Option 2: X's official MCP server and the X API

X runs a hosted MCP server at https://api.x.com/mcp, and its documentation says you need your own X developer app to use it. The X developer docs for MCP state that X's OAuth "requires your own developer app" and that the endpoint does not advertise native MCP OAuth discovery. There are two ways to authenticate. An app-only bearer token pasted into your client works for read-only endpoints and has no user context, so it cannot act as you. OAuth 2.0 user context goes through a local xurl mcp bridge that does a browser login, and the docs describe it as required for writes and any user-context tool.

The same page lists reading and searching posts, user lookups and timelines, bookmarks, and Articles among its capabilities. It also says that if an app is not enrolled you move it to "Pay-per-use" and "Production", and it warns that writes count against rate limits. The page I checked gives no price list, so check X's current terms before you build a workflow on it. X announced the hosted server in June 2026 on its developer community.

What this route is good at is breadth: Claude can look things up on X live. What it is not built to do is keep a daily record of how your own posts performed. Each answer is a live call, and a history over time is something you would have to build.

Option 3: an MCP server that keeps measured snapshots (LinkIntel)

LinkIntel is an MCP server that stores your own X post results as daily snapshots and gives them to Claude as a cited brief. After you connect X once through OAuth, it reads your recent original posts and their metrics every day, keeps the snapshots, and exposes them to Claude or any MCP-compatible assistant. The same brief includes X's published ranking weights, read daily from X's open-source code, with a link to the commit for each value. Read more on how those weights work in the X algorithm explained and on the X algorithm weights page.

The limits matter as much as the features. LinkIntel does not publish or schedule posts. It does not search X. It does not predict reach; the ranking weights describe what the ranker rewards, not how many views a post will get. You do not need an X developer account. It costs $39 USD a month with no free trial and a full refund within 7 days. LinkedIn is closed to new customers, so this is X only.

	X archive or analytics CSV	X's official MCP server	LinkIntel
Setup effort	Request an export, wait, paste	Create a developer app, configure auth, add the server	Add the server, sign in, connect X
Needs an X developer account	No	Yes, per X's docs	No
History over time	Only if you re-export	Live calls, no stored history	Daily snapshots of your posts
Includes X ranking weights	No	No	Yes, with commit links
Can post for you	No	Writes are limited per the docs (bookmarks, Articles)	No
Searches X	No	Yes	No
Cost	Free	Requires X's Pay-per-use API package, per X's docs	$39 USD a month

What each option can and cannot tell your assistant

Each route answers a different question, so the table above is a guide to fit and not a ranking. The archive tells Claude what you wrote. The official server tells it what X's API returns right now. LinkIntel tells it what your recent posts did over the days it has been measuring, and what X's ranking code currently rewards.

None of them tells Claude what a new post will do. Observed numbers on past posts are evidence for an angle worth testing, not proof that a style caused a result. A good assistant will say that, and a good source makes it easy by showing dates and sources.

Setting it up in Claude Code and Claude.ai

Setup takes one command in Claude Code or one connector in Claude.ai, then a browser sign-in. These steps come from the LinkIntel MCP docs and FAQ.

Claude Code

1. Run claude mcp add -s user --transport http linkintel https://www.getlinkintel.com/api/mcp.
2. Type /exit, then claude --continue, so the new session loads the server.
3. When prompted, finish sign-in in the browser. New customers confirm the $39 USD a month payment before access opens.
4. Ask the assistant to call get_data_status and follow the X connect link it offers.

Claude.ai or Claude Desktop

1. Open Settings, then Connectors, then Add custom connector.
2. Paste https://www.getlinkintel.com/api/mcp.
3. Press Connect on the first LinkIntel request and sign in.
4. Connect X when asked, then ask for a content brief on a topic.

You can also start from the connect page. After X is connected, snapshots build up daily, so a brief gets richer in the days that follow.

FAQ

Can Claude read my X analytics?

Not by itself. Claude needs a source it can read, such as an export you paste in, X's MCP server, or an MCP server that stores your measured posts.

Do I need an X developer account to give Claude my X data?

For X's official MCP server, yes: its docs say you use your own developer app. For an exported archive or LinkIntel, no.

Does LinkIntel post to X for me?

No. LinkIntel only reads. It does not publish, schedule or search X, and it does not predict reach.

How much does LinkIntel cost?

$39 USD a month, billed monthly in advance, with no free trial. There is a full refund within 7 days.

How is this different from a scheduler like Typefully?

Schedulers write, queue and publish posts. LinkIntel does neither; it gives the assistant you already use your measured results. See LinkIntel vs Typefully, Tweet Hunter and OpenTweet, or read what an MCP server for X post analytics is.