mcp-x
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-xpost a tweet: 'Learning about MCP servers today!'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-x MCP server
MCP project to connect Claude with X API. Built on top of X API v2
Demo
Supported Features
Post tweets
Configuration
Getting Started with X
Go to X Developer Platform and login with your X account
Start with Basic plan
Store the Access Token, Secret, Client ID, Client Secret and Bearer token Docs: x-api-start
Related MCP server: X MCP Server
Set up
On MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.jsonOn Windows:
%APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"x": {
"command": "uv",
"args": [
"--directory",
"PROJECT_PATH/src/mcp_x",
"run",
"mcp-x"
],
"env": {
"X_API_KEY": "YOUR_API_KEY",
"X_API_KEY_SECRET": "YOUR_API_KEY_SECRET",
"X_ACCESS_TOKEN": "YOUR_ACCESS_TOKEN",
"X_ACCESS_TOKEN_SECRET": "YOUR_ACCESS_TOKEN_SECRET",
"X_BEARER_TOKEN": "YOUR_BEARER_TOKEN",
"LOGGING_PATH": "PROJECT_PATH/src/mcp_x/logs"
}
}
}
}TODO
Tests
Add Get tweets
Add Delete tweets
...
Deployment
(todo)
Building and Publishing
To prepare the package for distribution:
Sync dependencies and update lockfile:
uv syncBuild package distributions:
uv buildThis will create source and wheel distributions in the dist/ directory.
Available Tools
1 toolx_PostTweetB
Post a tweet using the X API
| Name | Required | Description | Default |
|---|---|---|---|
| tweet_content | Yes | Content of the tweet |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral disclosure burden. It only states the action itself ('Post a tweet') without mentioning rate limits, error behavior, or whether authentication is required.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no redundant information. It is appropriately brief for a tool with one parameter.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description should explain what the tool returns or other operational details, but it does not. However, for a simple one-parameter tool, the description is minimally adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% (tweet_content is described as 'Content of the tweet'), so the baseline is 3. The description adds no additional parameter semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Post') and resource ('a tweet') clearly indicating the action. With no sibling tools, it fully distinguishes the tool's purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool, prerequisites (e.g., authentication), or context. There are no alternatives mentioned, so the agent has no information about suitable scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of confusing it with another. The purpose of x_PostTweet is clear and unambiguous.
The tool name combines a prefix 'x_' with CamelCase 'PostTweet', which mixes conventions but is still readable and suggests a consistent pattern if more tools existed. As a single tool, its name is clear and not chaotic.
A single tool is too few for a server purportedly for the X (Twitter) API, which has many operations. The server feels critically under-scoped, offering only posting functionality.
The tool surface covers only posting tweets, leaving out essential operations like reading, searching, or deleting tweets. This is severely incomplete for a server meant to interact with X.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
15 Twitter / X endpoints. Pay per call in USDC via x402.
X/Twitter reads, search, monitors and posting. Pay-per-call in USDC — no signup, no API keys.
X (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup.
Stop guessing what works on X/Twitter. Analyze your history, draft in your voice, schedule posts.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with X (formerly Twitter), allowing for posting tweets, searching content, managing accounts, and organizing lists.253MIT
- FlicenseBqualityDmaintenanceEnables users to interact with X (Twitter) through the X API. Supports posting tweets, retrieving user timelines, searching tweets, and replying to tweets with comprehensive error handling.315
- AlicenseBqualityDmaintenanceEnables creating, managing, and publishing X/Twitter posts, threads, and replies directly through Claude chat. Supports draft management with the ability to create, list, publish, and delete tweet drafts.101MIT
- AlicenseAqualityAmaintenanceEnables seamless interaction with Twitter/X platform through Claude AI, allowing users to post tweets with images, search for tweets, and engage in conversations using natural language commands.107425MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Lyonsupernova/mcp-x'
If you have feedback or need assistance with the MCP directory API, please join our Discord server