Your AI reads X as it is today,
not as it was at training time.
Once it's installed, Claude can go look things up on X by itself — find accounts, read timelines, check what's trending. 40 endpoints, no glue code, and no waiting in X's API approval queue.
claude mcp add socialapi -e SOCIALAPI_KEY=sk_your_key -- npx -y @socialapitech/mcp-serverThe model stopped learning. X didn't.
It has no idea what just happened
Every model has a cutoff date, and everything after it is a blank. This closes the gap — a tweet from ten minutes ago, a topic still climbing, an account that got suspended this morning.
One less layer to maintain
No HTTP wrapper to write, no pagination to handle, no cursors to wrangle. The model works out which tool to call and what to pass it.
Read-only, which is why it's safe to install
No posting, no liking, no following — you never hand over an X account at all. If a key leaks, someone gets a few extra queries, not your voice.
You ask. It figures out the rest.
What's @elonmusk been posting lately? And how many followers does he have now?
Nine of his last 20 posts are about the next Starship flight, five are reposts of the xAI launch… and he's sitting at 241M followers.
Which tools to call, and in what order — the model works that out on its own.
15 tools across 40 endpoints
Grouped by job on purpose. Listing all 40 endpoints as separate tools would flood the model's context and make its choices worse, not better.
x_user_profileProfile & biox_user_timelineTimeline (tweets, replies, media)x_searchAdvanced search, full X syntaxx_mentionsMentionsx_tweetTweet, replies, threadx_tweets_batchBatch tweetsx_follower_graphFollower / following graphx_relationshipRelationship between accountsx_trendsLive trends, by regionx_communityCommunities & membersx_listListsx_org_affiliatesOrg affiliatesx_account_dossierAccount dossier (one call)x_exploreExplore feedx_batch_profilesBatch profilesThree steps, about two minutes.
claude_desktop_config.jsonclaude mcp addmcp.jsonmcp_config.jsonMCP ServersAnything that speaks MCP will work — these are just the ones we ran ourselves.
claude mcp add socialapi -e SOCIALAPI_KEY=sk_your_key -- npx -y @socialapitech/mcp-server{
"mcpServers": {
"socialapi": {
"command": "npx",
"args": ["-y", "@socialapitech/mcp-server"],
"env": { "SOCIALAPI_KEY": "sk_your_key" }
}
}
}Need to watch an account? That's a different job.
MCP is request-and-response: the model looks something up because you asked. That's the right shape for research, due diligence, or just catching up on what someone's been posting.
But if what you want is "tell me the moment they post", we push to you instead — over WebSocket or a webhook, median two seconds from post to delivery. Same balance, nothing extra to sign up for.
See how monitoring is billed →Costs exactly the same as calling the API yourself
There is no separate MCP plan. Same balance, same rates — every tool call is one request, billed as if you had sent it yourself.
Let it go look for itself.
Get a key, paste one line, restart. Takes less time than reading this page did.