Media · Remote MCP server

X Twitter

X (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup.

Visit X Twitter's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.veezee/x-twitter
Version
1.1.0
Status
Active
Category
media
Transport
Streamable HTTP
Published
2026-07-14
Updated
2026-07-14
Publisher
io.veezee · 4 servers with pages here
Namespace
Namespace verified by the MCP Registry via the domain veezee.io · how
Listed under
X (Twitter) MCP servers
Website
veezee.io
Repository
github.com/veezeehq/veezee-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.veezee.io/xNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

How to connect X Twitter

X Twitter is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.veezee.io/x, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from io.veezee

All 4 →
ServerRunsEndpoint or package
AllReal-time LinkedIn, X (Twitter) and Reddit data for AI agents. Free key, self-minted, no signup.Remote · HTTPLive check: sign-in requiredmcp.veezee.io
LinkedinLinkedIn data for AI agents: search, profiles, companies, posts. Free key, self-minted, no signup.Remote · HTTPLive check: sign-in requiredmcp.veezee.io
RedditReddit posts, comments, subreddits, and search for AI agents. Free key, self-minted, no signup.Remote · HTTPLive check: sign-in requiredmcp.veezee.io

More media servers

All 1,985 →
ServerRunsEndpoint or package
X (Twitter) Trends MCPTwitter (X) trends over time, with growth for any keyword. Free key at trendsmcp.ai.Remote · HTTPLive check: ✓ handshakex-twitter.api.trendsmcp.ai
X Archive RAGLocal-first MCP tools for searching and drafting from your X/Twitter archive.Local · stdioMCP Bundle (.mcpb): mameshivaa/x-archive-rag/releases/download/v0.1.
X MCP AiSafety-first X (Twitter) API v2 MCP server: 41 typed tools across 12 packages, policy-gated.Local · stdionpm: x-mcp-ai
X TwitterX (twitter): x, xapi, Twitter, twitter api, twitters,tweets, tw, twttr, FollowerIds, friendsIds.Remote · HTTPLive check: ✓ handshakemcp.jojapi.com
X Twitter DataX (Twitter) data for AI agents: tweets, profiles, followers, search, trends + social listening.Remote · HTTPLive check: sign-in requiredmcp.superagnt.com
X Twitter Profile TweetsX (Twitter) profiles, tweets and single-tweet lookup by handle or URL. No login. Pay per result.Remote · HTTPLive check: sign-in requiredmcp.apify.com
x-useBrowser-native AI agents for X (Twitter): multi-account, MCP-ready, no X API key required.Local · stdioPyPI: x-use-mcp
x402-video MCPPay-per-call AI video generation over x402 (USDC on Base). No accounts, no API keys.Local · stdionpm: x402-video-mcp