mcpbeat Sign in

TweetAPI MCP Server

answering

TweetAPI MCP is answering right now. Last checked 12 min ago.

Read-only public Twitter data and TweetAPI docs for AI agents. Not affiliated with X Corp.

Uptime history 66 days of history · worst day 92%
66 days agonow
100.0%
Uptime 24h
89 of 89 checks
—
Tools
hidden behind auth
372 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check TweetAPI MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.tweetapi.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.tweetapi.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.tweetapi.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.tweetapi.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.tweetapi.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.tweetapi.com/mcp streamable-http sign-in 348 ms 12 min ago

Alternatives to TweetAPI MCP

same job, measured the same way
Twitter
by jojapi

X (formerly Twitter): X (formerly Twitter) public and private data API for search, posts (Tweets).

32 tools answering
Social Fetch
by social-freak-ltd

Public social-data API and live docs for AI coding agents.

251 tools answering
xdataapi: X (Twitter) data
by xdataapi

Read-only public X (Twitter) data: profiles, tweets, threads, followers, search. Pay per result.

14 tools answering
TwitterAPIs
by twitterapis

Official MCP server for twitterapis.com. Read and write Twitter/X: search, users, tweets, DMs.

137 installs/wk answering
TwittrAPI
by twittrapi

Read public Twitter/X data: tweets, profiles, followers, search. No X developer account.

264 installs/wk answering
Prowlo — Reddit & X for AI agents
by prowlo

Reddit & X data for AI agents over MCP. Semantic search, hosted, no Reddit API.

49 tools answering
All
by veezee

Real-time LinkedIn, X (Twitter) and Reddit data for AI agents. Free key, self-minted, no signup.

answering
Shippost MCP
by ryankramer

Twitter/X tools for AI agents — read timelines, post tweets, search, and engage

80 installs/wk local only

TweetAPI MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for TweetAPI MCP?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is TweetAPI MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 89 checks got a reply (100.0%), average response time 372 ms. The bar chart above shows every period we have measured.
How do I connect TweetAPI MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to TweetAPI MCP?
No API key is involved. TweetAPI MCP answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is TweetAPI MCP?
It answers our handshake in 372 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.