post_tweet
Post a new tweet to Twitter
LABSCO SUMMARY
Posting from the client you are in, with a tool list short enough to audit in one look.
Two tools, and one of them publishes to a live account: there is no draft, no edit and no delete in the surface, so whatever the agent decides to post is what ships. The read side is a query with a result count, which is enough to check what a thread is saying before you reply to it and not enough to do timeline analysis.
What it is
A two-call Twitter client: one write that posts a tweet or replies to an existing tweet id, and one read that searches tweets for a query.
What you get
- Posting a tweet from wherever the model is already working
- Replying to a specific tweet by its id, with the reply text in the same call
- A search over tweets for a query, returning the number of results you ask for
Requirements
Four Twitter API credentials: API_KEY, API_SECRET_KEY, ACCESS_TOKEN and ACCESS_TOKEN_SECRET.
Setup effort
One command plus a key — npx -y @enescinar/twitter-mcp, then supply credentials
USE CASES
01
Publishing an update or a reply without switching apps
One call posts the text; passing the id of an existing tweet makes it a reply in that thread rather than a standalone post.
02
Reading what is being said before you answer it
Search for a query and ask for as many results as you want to weigh, so the reply is written against the current conversation instead of a summary of it.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
search_tweets
Search for tweets on Twitter
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
- npx on PATH
- API_KEY in your environment
- API_SECRET_KEY in your environment
- ACCESS_TOKEN in your environment
- ACCESS_TOKEN_SECRET in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @enescinar/twitter-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"twitter-mcp": {
"command": "npx",
"args": [
"-y",
"@enescinar/twitter-mcp"
],
"env": {
"API_KEY": "<YOUR_API_KEY>",
"API_SECRET_KEY": "<YOUR_API_SECRET_KEY>",
"ACCESS_TOKEN": "<YOUR_ACCESS_TOKEN>",
"ACCESS_TOKEN_SECRET": "<YOUR_ACCESS_TOKEN_SECRET>"
}
}
}
}
