TweetAPI MCP Server

by tweetapi Your server? Claim it

answering

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

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

Uptime history 21 days of history · worst day 99%

21 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

545 ms

Response time

average over 24h

API key or OAuth

Access

streamable-http

TweetAPI MCP does not always answer

Over the last week it answered 99.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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, but you need an API key or OAuth to use it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.tweetapi.com/mcp	streamable-http	needs key	403 ms	3 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.

207 tools answering

TwitterAPIs

by twitterapis

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

149 installs/wk local only

Prowlo — Reddit & X for AI agents

by prowlo

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

47 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

72 installs/wk local only

Superpowers.social

by superpowers

Hosted MCP for X/Twitter and Reddit. 12 read-only tools, no API keys, free during beta.

10 tools answering

x-use

by ihuzaifashoukat

Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no X API key required.

196 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 91 of 91 checks got a reply (100.0%), average response time 545 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 will need your own key or an OAuth login: it refuses anonymous clients.

Does TweetAPI MCP need an API key?

Yes. Every time we knock, TweetAPI MCP answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is TweetAPI MCP?

It answers our handshake in 545 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.