{"id":"ryanmac-agent-twitter-client-mcp","name":"agent-twitter-client-mcp","homepage":"https://github.com/ryanmac/agent-twitter-client-mcp","repo_url":"https://github.com/ryanmac/agent-twitter-client-mcp","category":"communication","subcategories":[],"tags":["mcp","twitter","x","agent","integration","social-media","grok","typescript","nodejs"],"what_it_does":"Provides an MCP (Model Context Protocol) server that exposes Twitter/X actions (read tweets, search, post/like/retweet/quote, follow/profile data) to AI agents, including optional Grok chat/realtime features via the underlying agent-twitter-client integration.","use_cases":["Let an LLM/agent fetch tweets or user profile data and summarize or reason over it","Enable an agent workflow to search Twitter/X for topics and then take actions (e.g., post, like, follow)","Provide an MCP tool surface for Claude/Desktop (or other MCP hosts) to interact with Twitter without direct API access","Demo/experimental Grok-on-Twitter style interactions through the same MCP interface"],"not_for":["Production-grade, high-assurance deployments without review of auth and data-handling (uses cookie-based auth to Twitter)","Avoiding platform policy risk (posting/liking/following are high-impact actions)","Use as a general-purpose Twitter API replacement with stable guarantees (Twitter changes frequently; Grok has extra constraints)"],"best_when":"You want agent-to-Twitter functionality via MCP tools (e.g., Claude Desktop) and can supply the necessary Twitter credentials/cookies, accepting that Twitter/Grok behavior may vary and requires ongoing maintenance.","avoid_when":"You need strict OAuth scopes-based least privilege, domain-verified enterprise security controls, or you cannot securely manage Twitter credentials/cookies in an environment where agents may access them.","alternatives":["A direct Twitter API integration using OAuth 2.0","A server-side wrapper you control with finer-grained auth/permissions and audited logging","Other MCP servers that wrap social/streaming APIs with standard OAuth flows","For Grok-like experiences: official Grok APIs or approved integrations (if available for your use case)"],"af_score":67.8,"security_score":52.2,"reliability_score":41.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:29:55.918291+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["cookie-based authentication","username/password authentication","Twitter API v2 credentials (API key/secret and access tokens)"],"oauth":false,"scopes":false,"notes":"Auth is configured via environment variables (AUTH_METHOD with cookies/credentials/api). Cookie auth is recommended and requires auth_token/ct0/twid values; Grok access additionally depends on agent-twitter-client version and (per README) Premium requirements."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information for the MCP server itself is provided; costs/limits are likely dominated by Twitter/X and Grok/Twitter Premium constraints (as described for Grok rate limits)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":67.8,"security_score":52.2,"reliability_score":41.2,"mcp_server_quality":75.0,"documentation_accuracy":75.0,"error_message_quality":null,"error_message_notes":"Mentions common failure modes and logs (error.log/combined.log) and includes examples of expected cookie format and Grok rate limit behavior, but does not demonstrate standardized MCP error payloads in the provided content.","auth_complexity":40.0,"rate_limit_clarity":75.0,"tls_enforcement":90.0,"auth_strength":45.0,"scope_granularity":20.0,"dependency_hygiene":60.0,"secret_handling":50.0,"security_notes":"Strengths: supports environment-based credential configuration and uses an MCP server model (credentials not embedded in code per README). Concerns: cookie-based authentication to Twitter is high-risk (long-lived secrets; potential logging exposure if not carefully handled). Scope/granularity and least-privilege are not described; mutation tools (post/like/follow) increase impact if misused by an agent. TLS enforcement for the MCP transport is not explicitly documented in the provided content, but typical MCP servers use HTTPS/WebSockets when deployed; score reflects assumption. No dependency vulnerability/SBOM/CVE scanning info is provided.","uptime_documented":20.0,"version_stability":55.0,"breaking_changes_history":35.0,"error_recovery":55.0,"idempotency_support":"false","idempotency_notes":"Write actions exist (send_tweet/like/retweet/quote/follow). The provided docs do not indicate idempotency keys or safe retry semantics for mutations.","pagination_style":"none","retry_guidance_documented":true,"known_agent_gotchas":["Cookie authentication requires cookies in a specific JSON array format with proper domains; expired cookies will break auth.","Twitter/Grok may trigger Cloudflare/captcha especially for username/password auth (docs warn of this).","Grok functionality requires agent-twitter-client v0.0.19+; the package description/README notes current basic functionality uses v0.0.18 and demo flags may install v0.0.19.","Grok has rate limits (non-premium: 25 messages/2 hours per README) and the MCP returns rate limit info only when limits are reached.","Agent workflows may repeatedly trigger mutation tools unless the agent host implements throttling/guardrails."]}}