mcpField
🐦
🐦✨ MCP Twitter Post System

🐦✨ MCP Twitter Post System

Local
github.com/siddreddy07Social Media0Updated 73w ago

About 🐦✨ MCP Twitter Post System

An MCP server and Node.js client for posting tweets through the Twitter API. Its SSE-based client-server setup keeps tweet requests and posting logic in separate components.

Key features

  1. 01Post tweets through the Twitter API
  2. 02Communicate between client and server using SSE
  3. 03Send tweet commands from the command line
  4. 04Store API credentials in `.env`

Use cases

  1. 01Post a tweet from a command-line workflow
  2. 02Send tweet requests to a separate server
  3. 03Keep Twitter API credentials in an environment file

MCP support

The MCP server handles tweet commands and uses the Twitter API to post tweets; the included client communicates with it over HTTP or SSE.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json Β· Universal config
{
"mcpServers": {
"twitter-post": {
"command": "npx",
"args": [
"-y",
"nodemon"
]
}
}
}
Run commandnpx -y nodemon

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmnodemon

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

🐦✨ MCP Twitter Post System

Welcome to the MCP Twitter Post System β€” your go-to tool for launching tweets into the Twitterverse with real-time flair! πŸš€ Powered by Node.js, Server-Sent Events (SSE), and the Twitter API, this project is neatly split into client/ and server/ folders for a smooth, organized workflow. Get ready to tweet like a rockstar! 🌟


πŸ“‚ Project Structure

Here's the blueprint of the MCP Twitter Post System:

PathDescription
client/🌐 The MCP Client, your tweet-launching control hub
client/index.jsπŸš€ Fires off real-time tweet commands to the server
server/πŸ› οΈ The MCP Server, the genius behind the scenes
server/index.jsπŸ–₯️ Runs the HTTP server and SSE wizardry
server/mcptools.js🐦 Crafts tweets with Twitter API magic
.envπŸ”’ Safely stores your Twitter API keys
README.mdπŸ“– You're soaking in this epic guide right now!

πŸŽ‰ Features That Make Tweeting a Blast

  • ⚑ Real-Time Tweet Action: Send tweets straight from your command line in a flash!
  • πŸ“‘ Seamless SSE Connection: Client and server vibe together with Server-Sent Events.
  • 🐦 Twitter API Power: Post tweets securely using the Twitter API.
  • 🧩 Clean Separation: Client and server logic are organized like a pro.
  • πŸ” Safe Secrets: API keys stay secure in a .env file.

🌟 Spotlight: The MCP Server

The MCP Server is the heart and soul of this project! πŸ› οΈπŸ’₯ Housed in the server/ folder, it’s the powerhouse that listens for your tweet commands, orchestrates real-time communication via SSE, and seamlessly integrates with the Twitter API to make your tweets soar. Running on index.js and powered by mcptools.js, the MCP Server ensures every tweet is crafted with precision and posted securely. It’s like having a tweet-slinging superhero at your command! πŸ¦Έβ€β™‚οΈ


πŸ› οΈ Setup: Let’s Launch Your Tweet Machine!

1. Clone the Repo

Dive into the Twitterverse by grabbing the code:

git clone https://github.com/siddreddy07/mcp-server-twitter-post.git
cd mcp-twitter-post
2. Install Dependencies (If Needed)

Hop into both client/ and server/ folders and run:

npm install

No package.json? Skip this step and keep the tweet party rolling! πŸŽ‰

3. Configure Your Twitter API Keys

Create a .env file in the server/ folder and add your Twitter API credentials:

API_KEY=your_twitter_app_key
API_SECRET_KEY=your_twitter_app_secret
ACCESS_TOKEN=your_twitter_access_token
ACCESS_SECRET_TOKEN=your_twitter_access_secret

✨ Pro Tip: Snag these keys from the Twitter Developer Portal!


πŸš€ Running the Project

Start the MCP Server

Launch the MCP Server to handle your tweet requests:

cd server
npx nodemon index.js
Fire Up the MCP Client

Kick off the client to send tweets in real-time:

cd client
node index.js

Watch your CLI sparkle as your tweets take flight! 🐦✨


🧠 How It All Works

  1. Client (client/index.js): Your command center sends tweet data via HTTP or SSE. Type, hit enter, and BOOM β€” it’s off to the server! πŸš€
  2. Server (server/index.js): The MCP Server catches client commands and directs the tweet-posting action.
  3. Tools (server/mcptools.js): Works the Twitter API magic to craft and post tweets with style.
  4. Security: API keys stay locked in the .env vault, safe from prying eyes. πŸ”’

βš™οΈ Tech Stack That Rocks

  • Node.js: The engine driving this tweet-tastic journey.
  • Express (or native HTTP): Powers the MCP Server with slick efficiency.
  • Server-Sent Events (SSE): Keeps client-server communication lightning-fast.
  • Twitter API: Via twitter-api-v2 (or your favorite Twitter package).
  • Dotenv: Keeps your API keys cozy and secure. 😎

πŸ“ Quick Tips for Tweet Domination

  • πŸ›‘οΈ Ensure your Twitter Developer account is active and your app is approved.
  • πŸ”₯ Use nodemon for hot-reloading to keep the MCP Server development smooth.
  • πŸ’‘ Check the CLI for real-time tweet feedback.
  • 🌐 Explore the Twitter API Docs for advanced tweaks.

πŸ› Bugs or Brilliant Ideas?

We’re all about making this project shine! 🌟 Open an issue, submit a pull request, or tweet us your thoughts (manually for now πŸ˜‰) to join the fun.


Happy Tweeting! πŸŽ‰

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.