# X (Twitter) MCP MCP

> Use this X (Twitter) MCP to automate social intelligence workflows right from your agent. It lets you search for recent public discussions using keywords, fetch detailed profile information by username, or get the full engagement metrics for any specific tweet ID. Stop manually checking timelines; let your AI client pull structured data directly.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** social-listening, sentiment-analysis, engagement-metrics, content-discovery, profile-metadata, trend-analysis

## Description

You can connect your X (Twitter) developer account to your AI agent and take control of social listening without messy web scraping. Instead of navigating through endless feeds, you tell your agent exactly what you need: a list of people talking about a specific topic in the last seven days, or the full stats for a single post. The MCP lets your agent pull detailed profile data by username, giving you follower counts and bio text instantly. Need to audit how well an influencer is doing? Just provide the tweet ID, and you get the raw engagement numbers—likes, retweets, and replies. When you run these operations through Vinkius, all tool calls are cryptographically signed, creating a tamper-proof audit trail, so you know exactly what data your agent pulled and when. Your AI client becomes your eyes on the timeline.

## Tools

### get_tweet_details
Retrieves the text and engagement metrics from any specific tweet ID.

### get_tweet_volume
Returns time-series buckets showing how many tweets match a query. Great for spotting spikes in brand mentions or trending topics.

Get the volume of tweets matching a search query over the last 7 days, broken down by hour or day

### search_recent_tweets
Searches for recent public tweets (up to last 7 days) using keywords, hashtags, or handles.

### lookup_user_by_username
Fetches full details of a specific X user by their username (follower count, bio, verified status).

### lookup_users_batch
Pass usernames as a comma-separated string without the "@" symbol.

Fetch profile details of multiple X (Twitter) users at once by their @usernames (up to 100)

### get_tweets_batch
Pass IDs as a comma-separated string.

Retrieve text and engagement metrics for multiple tweets at once by providing their IDs (up to 100)

## Prompt Examples

**Prompt:** 
```
Search for tweets mentioning 'Vinkius Cloud' over the last couple days.
```

**Response:** 
```
I've fetched 8 recent tweets mentioning 'Vinkius Cloud'. The sentiment is mostly positive, praising the new LLM integrations. One user encountered a latency issue. Want me to summarize their exact complaint?
```

**Prompt:** 
```
Look up the profile details for 'elonmusk'.
```

**Response:** 
```
Profile fetched: Elon Musk is based in Austin, TX and currently has over 180M followers. His bio reads '...'. Should I retrieve his most recent tweets?
```

**Prompt:** 
```
Get the engagement stats for tweet ID 123456789.
```

**Response:** 
```
The tweet 'Just shipped the new API v2!' has 4,500 likes, 320 retweets, and 12 replies so far. The engagement rate seems healthy based on your average metrics.
```

## Capabilities

### Search for specific content
Find recent public discussions across the network using exact keywords or hashtags.

### Get user profile metadata
Fetch complete details about a specific X user, including their follower count and verified status.

### Extract tweet engagement data
Retrieve the text content and all metrics—likes, retweets, replies—from any given tweet ID.

## Use Cases

### Competitor monitoring after launch
A product researcher needs to know what people are saying about the new market leader. They ask their agent to use `search_recent_tweets` for competitor names over the last week, then summarize the common complaints found.

### Verifying an influencer's reach
A marketing manager needs proof of a micro-influencer's authority. They use `lookup_user_by_username` to confirm follower counts and verified status before signing a contract.

### Measuring content effectiveness
Someone posts an announcement tweet. To measure its success, they give the agent the tweet ID and call `get_tweet_details`. The resulting data shows exactly how many likes it got versus retweets.

### Tracking a brand's reputation
A founder needs to monitor mentions of their company name. They use `search_recent_tweets` for the last seven days and ask the agent to categorize the sentiment found across all results.

## Benefits

- Identify emerging topics fast. Use the search function to pull lists of recent tweets about competitors or niche keywords, allowing you to respond early when sentiment shifts.
- Audit influencer performance accurately. Get precise profile metadata using `lookup_user_by_username` to check current follower counts and bios without guessing.
- Analyze post impact instantly. With `get_tweet_details`, you get raw numbers—likes, retweets, replies—allowing you to measure true content engagement rates.
- Process large data sets with minimal effort. Your agent handles the complex API queries that used to require hours of manual work in a dashboard.
- Build multi-step intelligence workflows. You can chain this MCP with other services within Vinkius to build automations that span multiple platforms using one AI client.

## How It Works

The bottom line is that instead of clicking through multiple web pages, your agent handles the whole process for you.

1. Subscribe to this MCP and enter your X (Twitter) App Bearer Token credentials.
2. Instruct your agent on the data you need. For example, 'Find all mentions of our competitor in the last week.'
3. The agent executes the necessary tool calls against the secure Vinkius platform and returns structured, actionable data.

## Frequently Asked Questions

**How do I use search_recent_tweets to track a competitor?**
Just provide the exact keyword or hashtag in your query. The MCP searches for public tweets mentioning that term over the last seven days, giving you a list of discussions.

**Can get_tweet_details tell me if a tweet was successful?**
It provides all the numbers needed to judge success: likes, retweets, and replies. You can feed those metrics into your agent for analysis.

**Does lookup_user_by_username need an @ symbol?**
No. When using `lookup_user_by_username`, you only provide the username without the '@' symbol, making the call cleaner and more reliable.

**Is this MCP good for sentiment analysis?**
It provides all the raw data—the text from the search results and the tweet details—that your agent needs to run its own sentiment analysis.

**What is the time limit for using search_recent_tweets?**
The tool searches public discussions up to the last seven days. This limitation covers recent, available content across the network. You won't find historical archives or deeply buried posts.

**How is authentication handled when running lookup_user_by_username?**
The platform uses a zero-trust proxy for credentials. Your Bearer Token passes through in transit but never gets stored on disk. This keeps your keys secure while the agent works.

**Are there rate limits I need to worry about with get_tweet_details?**
Vinkius manages throttling and API adherence for you. The platform handles the underlying service rate limiting, so you just focus on what data you need from a specific Tweet ID.

**What kind of data does lookup_user_by_username retrieve?**
It pulls public profile metadata like follower count, verified status, and the user's bio. It only accesses publicly available information associated with the account.

**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 show me how many followers a user has or where they are located?**
Absolutely. Providing the agent with the user's handle will invoke the lookup tool. It returns exactly what the developer sees: follower metrics, account description, and geographic location if public.