MCP Twitter Post System

@siddreddy07

Repository

Basic information

About MCP Twitter Post System

No overview available yet

#mcp-server#twitter-post#tweet-launcher

MCP Twitter Post System config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-server-twitter-post": {
      "command": "npx",
      "args": [
        "nodemon",
        "index.js"
      ]
    }
  }
}

MCP Twitter Post System tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is MCP Twitter Post System?

MCP Twitter Post System is a tool that enables posting tweets from the command line using Node.js, Server-Sent Events (SSE), and the Twitter API. It is split into a client folder and a server folder, making it suitable for developers who want to send tweets programmatically via an MCP-style client‑server architecture.

How to use MCP Twitter Post System?

Clone the repository, install dependencies with npm install in both client/ and server/, then create a .env file in the server/ folder with your Twitter API keys. Start the server with npx nodemon index.js from the server/ directory, then run the client with node index.js from the client/ directory. Tweets are sent from the command line.

Key features of MCP Twitter Post System

Real‑time tweet posting from the command line
Client‑server communication using Server‑Sent Events (SSE)
Twitter API integration via the mcptools.js module
Clean separation of client and server code
API keys stored securely in a .env file
Hot‑reloading support with nodemon during development

Use cases of MCP Twitter Post System

Posting tweets directly from a terminal without opening a browser
Automating tweet workflows as part of a larger Node.js application
Testing Twitter API interactions with a lightweight client‑server setup
Prototyping MCP (Model Context Protocol) style integrations

Frequently asked questions

What runtime and dependencies are required?

Node.js is required. The server uses Express (or native HTTP) and the `twitter-api-v2` package; the client and server both need `npm install` to fetch dependencies.

Where are my Twitter API keys stored?

API keys are stored in a `.env` file located in the `server/` folder. The file must contain `API_KEY`, `API_SECRET_KEY`, `ACCESS_TOKEN`, and `ACCESS_SECRET_TOKEN`.

How does the server communicate with the client?

The server uses Server‑Sent Events (SSE) to push real‑time updates to the client when a tweet command is issued.

How do I start the MCP Server?

Run `cd server` then `npx nodemon index.js` (or `node index.js`). This starts the HTTP server that listens for tweet commands.

What is the project structure?

The project contains two main folders: `client/` (the MCP Client that sends tweet commands) and `server/` (the MCP Server that handles Twitter API calls).

Comments

More Other MCP servers

Klarix Intelligence Engine

Klarix

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.

Volley.sh

Volley

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi