4,500+ servers built on MCP Fusion
Vinkius

X (Twitter) MCP. Analyze Public Sentiment and Engagement Metrics

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

X (Twitter) MCP on Cursor AI Code Editor MCP Client X (Twitter) MCP on Claude Desktop App MCP Integration X (Twitter) MCP on OpenAI Agents SDK MCP Compatible X (Twitter) MCP on Visual Studio Code MCP Extension Client X (Twitter) MCP on GitHub Copilot AI Agent MCP Integration X (Twitter) MCP on Google Gemini AI MCP Integration X (Twitter) MCP on Lovable AI Development MCP Client X (Twitter) MCP on Mistral AI Agents MCP Compatible X (Twitter) MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

X (Twitter) MCP Server gives your AI client direct access to X's public API tools. You search for recent tweets using keywords or hashtags, pull detailed profile metadata by username, and get granular engagement metrics from specific tweet IDs.

It lets you run social listening workflows—like monitoring a brand mention or checking competitor sentiment—all through natural conversation without writing complex scraping code.

What your AI agents can do

Get tweet details

Retrieves the text and all engagement metrics for a single Tweet ID you provide.

Lookup user by username

Fetches full profile data—including follower count, bio, and verification status—for any specified X (Twitter) user.

Search recent tweets

Searches for public tweets using keywords, hashtags, or handles published within the last seven days.

Find specific public discussions

You tell your agent a topic, and it searches for recent tweets matching keywords, hashtags, or names within the last week.

Retrieve user profile data

You give the agent an @username, and it pulls structured metadata like follower count, bio, and verified status.

Audit tweet performance metrics

You provide a Tweet ID, and the server returns the exact text alongside hard numbers for likes, retweets, and replies.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

X (Twitter): 3 Tools for Social Listening

These three tools let you search public tweets, look up user profiles, and inspect individual tweet engagement data through your AI agent.

get019d7616

get tweet details

Retrieves the text and all engagement metrics for a single Tweet ID you provide.

lookup019d7616

lookup user by username

Fetches full profile data—including follower count, bio, and verification status—for any specified X (Twitter) user.

search019d7616

search recent tweets

Searches for public tweets using keywords, hashtags, or handles published within the last seven days.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with X (Twitter), then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

X (Twitter) MCP Server - Analyze Social Data

Forget writing complex scrapers or wrestling with API key limits. This server gives your AI client direct, structured access to X's public data using the full capabilities of their API. You don't need a developer degree or hours spent in Postman; you just talk to your agent like normal and it handles the data retrieval.

Finding Specific Discussions

You can make your agent search for recent conversations across the platform. Just give it keywords, hashtags, or names—it pulls public tweets that match those criteria from within the last seven days. This is perfect when you're trying to monitor a specific topic or check out what people are saying about a competitor right now.

It handles searching using multiple filters simultaneously, so whether you want to track a general idea or zero in on a niche community, it finds the relevant tweets published recently.

Auditing Tweet Performance Metrics

When you've found a tweet that looks interesting, you don't just get the text. You provide your agent with the specific Tweet ID, and it pulls back all the hard numbers attached to that post. This means you instantly get the full content text alongside the exact counts for likes, retweets, and replies.

It’s not some estimate; it’s the raw data showing how widely that piece of content was spread and what kind of engagement it generated. You can analyze performance metrics on demand without running complex reporting tools.

Retrieving User Profile Data

You need to know who's talking? Give your agent an @username, and it fetches the full profile data for you. This structured metadata includes the user’s bio text, their current follower count, and whether or not they have a verified status badge. You can use this info to quickly assess credibility or understand the scope of influence behind an account before making any decisions about the content.

How It Works in Practice

Your AI client manages the whole process. For instance, you tell your agent: “Check out what people are saying about our new product launch,” and it automatically executes a search for keywords within the last week. If one of those tweets looks promising, you can ask it to pull the details on that specific tweet ID—getting the text, likes, retweets, and replies all in one go.

You can then follow up by asking your agent to check the profile data on the user who posted it, confirming their follower count and bio before moving on.

The server structure handles these three core functions together: searching for posts, checking out profiles, and deep-diving into individual post metrics. It keeps everything contained and structured, meaning you get clean JSON outputs every time—no messy HTML scraping needed. You just talk to your agent, and it pulls the necessary data points from X's public API.

It’s designed for social listening workflows: monitoring brand mentions, tracking competitor sentiment, or simply auditing how a piece of content performs right after it goes live. It keeps you in the loop on real-time discussions without making you write a single line of code.

How X (Twitter) MCP Works

  1. 1 Subscribe to this MCP Server on Vinkius.
  2. 2 Enter your X (Twitter) App Bearer Token into your preferred AI client's settings.
  3. 3 Tell your agent what you need—for example, 'Search for recent tweets mentioning quantum computing.' The agent runs the tool and gives you structured data.

The bottom line is: Your AI agent becomes a dedicated social intelligence worker that reads X (Twitter) public data for you.

Who Is X (Twitter) MCP For?

This server is for anyone whose job requires keeping tabs on the public conversation. It's for the brand manager who needs to know how fast a niche topic is trending, or the product researcher tired of manually pulling competitor mentions from multiple dashboards. If you need real-time social metrics, this is what you use.

Brand Manager

Runs daily searches for brand mentions and specific keywords to catch sentiment shifts early.

Product Researcher

Pulls lists of recent tweets about competitor products, then asks the agent to summarize common user pain points into a report.

Marketing Analyst

Checks specific influencer profiles using lookup_user_by_username to audit their follower count and most talked-about content.

What Changes When You Connect

  • Pinpoint brand mentions instantly. Use search_recent_tweets to track keywords or hashtags, letting you respond fast when a topic takes off.
  • Audit competitors' reach. Run lookup_user_by_username to pull verified status and follower counts for any account in minutes.
  • Gauge the impact of specific posts. Pass a Tweet ID to get_tweet_details to get hard numbers on likes, retweets, and replies.
  • Stop guessing about sentiment. The combination of searching (search_recent_tweets) and inspecting individual tweets gives you actionable data points.
  • Keep your agent focused. It handles the complexities of API calls so you only deal with clean, structured JSON output.

Real-World Use Cases

01

Tracking a new competitor launch

A product researcher wants to know how people are reacting to 'Competitor X's new feature'. They ask their agent to use search_recent_tweets with the keyword. The agent returns dozens of tweets, which they then feed back into the LLM to summarize common complaints and praise.

02

Verifying an influencer's reach

A marketing team needs to know if a potential partner is legit. They use lookup_user_by_username on the handle, checking for verification status and follower count before committing resources.

03

Deep-diving into one viral post

A social media manager finds a highly engaged tweet but needs more data. They grab the Tweet ID and run get_tweet_details. This confirms if the high engagement was due to shares or just likes, helping them adjust their strategy.

04

Monitoring an industry crisis

A founder tracks a niche keyword related to regulatory changes. They use search_recent_tweets daily. The agent collects the threads and provides a running summary of emerging fears or compliance questions across the network.

The Tradeoffs

Trying to find private conversations

Asking the agent to 'Check my direct messages about this product.' The server can't do that. It only accesses public data.

If you need to track a topic, use search_recent_tweets with specific keywords or handles. This limits your search scope to publicly visible content.

Assuming the profile is fully accurate

Thinking that just because a user mentions your brand, they are a verified expert. The agent can only provide metadata found via lookup_user_by_username.

Always cross-reference key accounts using lookup_user_by_username. Check the verification status and follower count to gauge credibility.

Overlooking tweet context

Just seeing a number like '4,500 likes' without knowing if that post was highly visible or niche. This leads to poor resource allocation.

Always use get_tweet_details when you find a promising Tweet ID. It gives the full picture of engagement (likes, retweets) for accurate analysis.

When It Fits, When It Doesn't

Use this server if your primary goal is to monitor public opinion or measure social reach using publicly visible data. You need real metrics: how many people saw it (get_tweet_details), who said it (profile metadata via lookup_user_by_username), or what the general conversation is around a topic (search_recent_tweets).

Don't use this if you need to access private data—DMs, emails, or internal company platforms. If your task involves analyzing unstructured text that isn't from X (Twitter), use specialized NLP tools instead. This server is strictly for the public timeline.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by X (Twitter). All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 3 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

get_tweet_details lookup_user_by_username search_recent_tweets

Tracking brand mentions used to mean manual scraping and endless tabs.

Today, monitoring a niche keyword means setting up multiple alerts across different social media sites. You copy-paste links into spreadsheets, manually checking for sentiment shifts or competitor buzz. It's slow, tedious, and you always miss the peak conversation because you weren't looking at it 24/7.

With this MCP server, your agent does the heavy lifting. You just tell it to 'Search for recent tweets mentioning our product.' The `search_recent_tweets` tool pulls all that public data into a clean list, letting you focus on what matters: the actual conversation.

X (Twitter) MCP Server allows you to get specific profile metrics.

Before, figuring out if an influencer was worth paying required checking their bio multiple times and guessing at their true reach. You'd copy the username and search Google for vague numbers, leading to wasted effort and bad decisions.

Now, just give the agent a handle. The `lookup_user_by_username` tool instantly returns concrete data—the verified status, exact follower count, and bio details—so you know exactly who you're dealing with.

Common Questions About X (Twitter) MCP

How do I search for tweets using the X (Twitter) MCP Server? +

You use search_recent_tweets by providing a query string. You can specify keywords, hashtags, or handles to narrow down your results from the last seven days.

Can I get engagement data for an old tweet ID using X (Twitter) MCP Server? +

Yes, use get_tweet_details. You supply the numeric Tweet ID and immediately receive the text alongside precise metrics like likes and retweets.

Does lookup_user_by_username require a specific format? +

No. Just give your agent the user's handle, without the '@' symbol. The tool fetches all available profile data for that account.

What is the limit on searching tweets with X (Twitter) MCP Server? +

The search capability uses keywords and hashtags but limits results to public discussions published within the last seven days. It won't pull historical archives.

How do I authenticate the X (Twitter) MCP Server? +

You connect using an X (Twitter) App Bearer Token. You must provide this token during setup so your AI client can securely access the necessary API endpoints.

When using `search_recent_tweets`, what is the maximum time range available? +

The tool searches for public tweets from the last 7 days. You cannot search for historical content outside of this recent timeframe via this server.

If I use `lookup_user_by_username`, what happens with private or deleted accounts? +

The tool will fail to retrieve data and return an error. You must ensure the account is public for a successful lookup of metadata like follower count or bio.

For `get_tweet_details`, must I provide the full numeric Tweet ID? +

Yes, this tool requires only the specific numerical Tweet ID. It cannot accept handles or descriptive text to find engagement metrics.

Can my AI search for tweets containing a specific competitor's hashtag? +

Yes. Ask the agent to run a recent search tool utilizing your query (e.g., '#competitor'). It will grab the last 10 matching tweets within seconds, giving you raw sentiment and user commentary without opening the app.

How far back in time can the agent search for tweets? +

The tool uses the standard v2 API limited to Recent Searches. This means the agent can perfectly fetch any matching tweets published in the last 7 days. It is optimized for reactive, fast-paced monitoring workflows.

Can it tell me if a specific user is verified or how many followers they have? +

Absolutely. Providing the agent with the user's handle will invoke the lookup tool. It returns exactly what the developer sees: the verified status, follower metrics, account description, and geographic location if public.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 3 tools

We've already built the connector for X (Twitter). Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 3 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.