Media · Local MCP server
Twitterapi
Read/write X (Twitter) via twitterapi.io: mentions, thread context, create and delete tweets.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.pedrot95dev/twitterapi- Version
- 0.1.2
- Status
- Active
- Category
- media
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-03
- Updated
- 2026-07-03
- Publisher
- pedrot95dev (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/pedrot95dev) · how
- Listed under
- X (Twitter) MCP servers
- Repository
- github.com/pedrot95dev/twitterapi.mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @pedrot95dev/twitterapi.mcp | 0.1.2 | stdio |
How to connect Twitterapi
Twitterapi runs locally from a Node.js package published to the npm registry: @pedrot95dev/twitterapi.mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @pedrot95dev/twitterapi.mcp@0.1.2. It reads these environment variables: TWITTERAPI_IO_KEY (required, secret), TWITTERAPI_IO_AUTH_TOKEN (secret), TWITTERAPI_IO_CT0 (secret) and TWITTERAPI_IO_PROXY (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"twitterapi": {
"command": "npx",
"args": [
"-y",
"@pedrot95dev/twitterapi.mcp@0.1.2"
],
"env": {
"TWITTERAPI_IO_KEY": "<secret>",
"TWITTERAPI_IO_AUTH_TOKEN": "<secret>",
"TWITTERAPI_IO_CT0": "<secret>",
"TWITTERAPI_IO_PROXY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. 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 pedrot95dev (GitHub)
| Server | Runs |
|---|---|
| RecapfyAsk about a YouTube video or fetch its transcript. Paid per call in USDC on Solana via x402. | Local · stdio |
More media servers
| Server | Runs |
|---|---|
| Twitter Agent by Nova (CIVAI)I do everything related to Twitter posting and campaigns. | Remote · HTTPLive check: ✓ handshake |
| Twitter Signal MCPLive X/Twitter search, profiles, leads, pain points, bot checks, AI digests. Paid per call, x402. | Local · stdio |
| Twitter X AioTwitter: Access real-time Twitter/X data as soon as it's posted. With the Twitter/X AIO API, you. | Remote · HTTPLive check: ✓ handshake |
| Twitter/X MCPRead public X posts, replies, profiles, and search results through Rettiwt or the official API. | Local · stdio |
| Twitterapi Io MCP ServerOfficial MCP server for twitterapi.io - Twitter/X data (tweets, users, followers, trends). | Local · stdio |
| Twitterapi MCP ServerTwitter/X read-only MCP server - 12 tools: search, users, tweets, followers, timelines, trends. | Remote · HTTPLive check: ✓ handshake |
| TwitterAPIsOfficial MCP server for twitterapis.com. Read and write Twitter/X: search, users, tweets, DMs. | Remote & Local · HTTP, stdioLive check: sign-in required |
| twscrape Twitter/X (read-only)Read-only X/Twitter MCP: posts, threads, replies, search via twscrape. No API key. | Local · stdio |