A
license-
qualityC
maintenanceEnables AI agents to fully automate X/Twitter interactions including searching, posting, engaging, and managing multiple accounts without paid API keys.
Last updated
MIT
x-twitter
by io.veezee
Server Details
X (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- veezeehq/veezee-mcp
- GitHub Stars
- 0
- Server Listing
- Veezee
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.6/5.0
Tool DescriptionsA
Average 4.9/5 across 7 of 7 tools scored.
Server CoherenceA
Disambiguation5/5
All seven tools have distinct purposes: get_usage for account limits, mint_key for API key creation, x_get_profile for user profile, x_get_tweet for a single tweet, x_get_tweets for timeline, x_resolve_url for URL resolution, and x_search for keyword search. Descriptions clearly differentiate overlapping areas like profile vs search/people and single tweet vs timeline.
Naming Consistency3/5
Most tools use snake_case and a verb_noun pattern, but there is inconsistency in the prefix: get_usage and mint_key lack the 'x_' prefix present on other tools (e.g., x_get_profile, x_search). Verbs also vary (get, mint, resolve, search), though all are imperative and generally clear.
Tool Count5/5
With 7 tools, the server is well-scoped for a Twitter data retrieval server. It includes essential admin tools (get_usage, mint_key) and core data tools (profile, tweet, timeline, search, URL resolution), neither too few nor too many for its purpose.
Completeness4/5
The tool surface covers key read operations for Twitter: profile data, tweets, timelines, search, and URL resolution. Minor gaps exist, such as missing tools for retrieving followers, likes, or trends, but the set is sufficient for many common tasks and avoids critical dead-ends.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseBqualityAmaintenanceEnables AI agents to search, read user profiles, timelines, media, follow threads, track trends, and manage accounts on X/Twitter via GraphQL, without browser automation or paid API keys.Last updated1008MIT
- Alicense-qualityDmaintenanceProvides AI agents and coding assistants with Twitter data access including tweets, user profiles, followers, and search functionality.Last updatedMIT
- Alicense-qualityCmaintenanceEnables AI agents to automate Twitter/X interactions with over 140 tools, requiring no API key.Last updated335428Apache 2.0
Try in Browser
Your Connectors
Sign in to create a connector for this server.