delete_tweet
Delete a tweet by its ID
LABSCO SUMMARY
A publishing and correction path, not a way to watch the account.
Post, search and delete is the whole surface — no timeline read, no direct messages, no likes or follows — so it fits an agent that writes to X rather than one that monitors it. Replies go through the same posting tool by passing the tweet being answered, which means a search result can be replied to on the next call.
What it is
A small X client: post, search and delete, acting as the account whose API credentials it holds.
What you get
- A tweet posted with text, optional media attachments, and an optional tweet it replies to
- A tweet search returning a chosen number of results for a query
- A tweet deleted by its ID
Requirements
X API credentials for the posting account in four environment variables: API_KEY, API_SECRET_KEY, ACCESS_TOKEN and ACCESS_TOKEN_SECRET.
Setup effort
One command plus a key — npx -y @mbelinky/x-mcp-server, then supply credentials
USE CASES
01
Replying to a post without opening the app
Search for the post you want to answer, then publish the reply against its ID, with media attached if the answer needs it.
02
Taking down a post that went out wrong
Find the post to get its ID, then delete it.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
post_tweet
Post a new tweet to X with optional media attachments
search_tweets
Search for tweets on X
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. delete_tweet relies on a v1.1 fallback that only OAuth 1.0a can use, and the v2 delete endpoint currently returns 500 errors. Base64 images do not work from Claude.
Requires
- npx on PATH (Node.js 18 or newer)
- An X Developer account with an app created in the Developer Portal, set to Read and write permissions
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @mbelinky/x-mcp-serverMCP Clients
Claude Desktop — OAuth 1.0a
CLAUDE DESKTOP — OAUTH 1.0A · JSON
{
"mcpServers": {
"twitter-mcp": {
"command": "npx",
"args": [
"-y",
"@mbelinky/x-mcp-server"
],
"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>"
}
}
}
}Windows %APPDATA%\Claude\claude_desktop_config.json · macOS ~/Library/Application Support/Claude/claude_desktop_config.json
Claude Desktop — OAuth 2.0
CLAUDE DESKTOP — OAUTH 2.0 · JSON
{
"mcpServers": {
"twitter-mcp": {
"command": "npx",
"args": [
"-y",
"@mbelinky/x-mcp-server"
],
"env": {
"AUTH_TYPE": "oauth2",
"OAUTH2_CLIENT_ID": "<YOUR_OAUTH2_CLIENT_ID>",
"OAUTH2_CLIENT_SECRET": "<YOUR_OAUTH2_CLIENT_SECRET>",
"OAUTH2_ACCESS_TOKEN": "<YOUR_OAUTH2_ACCESS_TOKEN>",
"OAUTH2_REFRESH_TOKEN": "<YOUR_OAUTH2_REFRESH_TOKEN>"
}
}
}
}Claude Code — OAuth 1.0a
CLAUDE CODE — OAUTH 1.0A · TERMINAL
claude mcp add twitter-mcp --scope user \
--env "API_KEY=<YOUR_API_KEY>" \
--env "API_SECRET_KEY=<YOUR_API_SECRET_KEY>" \
--env "ACCESS_TOKEN=<YOUR_ACCESS_TOKEN>" \
--env "ACCESS_TOKEN_SECRET=<YOUR_ACCESS_TOKEN_SECRET>" \
-- npx -y @mbelinky/x-mcp-serverClaude Code — OAuth 2.0
CLAUDE CODE — OAUTH 2.0 · TERMINAL
claude mcp add twitter-mcp --scope user \
--env "AUTH_TYPE=oauth2" \
--env "OAUTH2_CLIENT_ID=<YOUR_OAUTH2_CLIENT_ID>" \
--env "OAUTH2_CLIENT_SECRET=<YOUR_OAUTH2_CLIENT_SECRET>" \
--env "OAUTH2_ACCESS_TOKEN=<YOUR_OAUTH2_ACCESS_TOKEN>" \
--env "OAUTH2_REFRESH_TOKEN=<YOUR_OAUTH2_REFRESH_TOKEN>" \
-- npx -y @mbelinky/x-mcp-server
