X (Twitter) MCP Server

X (Twitter) MCP server enabling AI agents to interact with X's social platform — posting tweets and threads, searching tweets, retrieving user timelines, fetching engagement metrics, and integrating X's real-time social data into agent-driven social media management and monitoring workflows.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Social Media twitter x social-media mcp-server tweets x-api social-listening
⚙ Agent Friendliness
60
/ 100
Can an agent use this?
🔒 Security
80
/ 100
Is it safe for agents?
⚡ Reliability
59
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
60
Documentation
65
Error Messages
62
Auth Simplicity
48
Rate Limits
62

🔒 Security

TLS Enforcement
100
Auth Strength
80
Scope Granularity
78
Dep. Hygiene
62
Secret Handling
78

HTTPS. OAuth 2.0/1.0a. GDPR. Community MCP. Secure all four OAuth credentials. Minimum permissions scope.

⚡ Reliability

Uptime/SLA
68
Version Stability
58
Breaking Changes
52
Error Recovery
58
AF Security Reliability

Best When

An agent needs to post to X or perform limited social listening — content publishing, basic search, or monitoring within X API's strict rate limits.

Avoid When

You need high-volume tweet reading or scraping — X's API pricing ($100/month minimum for basic access beyond free) makes heavy use expensive.

Use Cases

  • Posting tweets and threads from social media management agents
  • Searching tweets for topics or keywords from social listening agents
  • Retrieving user timelines and engagement data from analytics agents
  • Monitoring brand mentions from reputation management agents
  • Generating social media content from content creation agents
  • Tracking trending topics and hashtags from market research agents

Not For

  • High-volume tweet reading (X API free tier is extremely limited)
  • Mass automated posting (violates X ToS; account risk)
  • Teams needing Instagram or LinkedIn (use those specific MCPs)

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
Yes

Authentication

Methods: oauth2 api_key
OAuth: Yes Scopes: Yes

X API v2 OAuth 2.0 (for user context) or Bearer Token (app-only). X Developer App required. API key + secret + access token + access token secret for OAuth 1.0a (for write operations). Complex multi-token setup.

Pricing

Model: freemium
Free tier: Yes
Requires CC: Yes

X API pricing dramatically increased after 2023. Free tier allows posting but very limited reading. Basic tier ($100/month) for meaningful read access. Pro tier is very expensive. Community MCP is free.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • X API pricing is extremely expensive beyond free tier — $100/month minimum for meaningful access
  • Four-part OAuth credential set required: API key, API secret, access token, access token secret
  • Rate limits are per-endpoint and per-window: 15 requests/15 minutes on free tier
  • Free tier is essentially write-only — reading tweets requires paid subscription
  • X API has undergone massive changes post-2022 — community MCPs may lag API version
  • Community MCP — X API changes frequently under new ownership; verify current endpoint compatibility

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for X (Twitter) MCP Server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6470
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered