Utilizes Supabase as a persistent storage backend to manage monitored accounts, track tweet data, and store engagement history for long-term ROI and performance analytics.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Engagio MCPShow me the top 5 engagement opportunities for #buildinpublic"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Engagio MCP
Twitter engagement intelligence for Claude Code. Find high-value tweets, post strategic replies, track performance.
What It Does
Monitor accounts - Track tweets from people you want to engage with
Monitor topics - Track hashtags and keywords (#buildinpublic, AI agents)
Score opportunities - Rank tweets by engagement velocity + author reach
Post replies - Reply directly from Claude with queue spacing
Track analytics - See which accounts give you the best engagement ROI
Timing insights - Learn when your replies perform best
Setup
1. Install dependencies
2. Configure environment
Create .env file:
3. Set up database
Create these tables in Supabase:
4. Add to Claude Code
Add to your .mcp.json:
Restart Claude Code.
Usage
Monitor accounts
Monitor topics
Find opportunities (cost-optimized)
Engage
Track performance
Thread context
Scoring Algorithm
Tweets are scored by engagement velocity weighted by author reach:
Higher engagement = higher score
Newer tweets = higher score
Replies weighted highest (conversation value)
More followers = higher multiplier (log scale to prevent domination)
Architecture
Tools Reference
Account Management
Tool | Description |
| Monitor a Twitter account (auto-fetches bio) |
| Add multiple accounts with rate limit handling |
| Stop monitoring |
| Remove multiple accounts |
| List monitored accounts with bios/notes |
| Fetch bios for accounts missing them |
| Add accomplishments/context |
Topic Management
Tool | Description |
| Monitor a hashtag or keyword |
| Stop monitoring topic |
| List monitored topics |
| Fetch tweets for topics |
Tweet Discovery (Cost-Optimized)
Tool | Description | Cost |
| Fetch from top N accounts by followers | ~$0.015 |
| Fetch from single account | ~$0.0015 |
| Fetch from ALL accounts | ~$0.09 |
| Ranked opportunities with filters | FREE |
| Search cached tweets | FREE |
| Search Twitter API | costs $ |
| Get tweet details | FREE |
| Get full thread context | FREE |
fetch_tweets parameters:
username: Fetch single account onlytop_n: Limit to top N accounts by followersskip_recent_hours: Skip accounts fetched within X hours (default: 2)
Engagement
Tool | Description |
| Post a reply immediately |
| Post original tweet |
| Add reply to queue (15min spacing) |
| View pending replies |
| Post next due reply |
| Clear reply queue |
Analytics
Tool | Description |
| Your recent replies |
| Update engagement stats |
| Overall engagement analytics |
| ROI per monitored account |
| Best posting times |
Cost Optimization
Built-in Rate Limiting
3 second minimum between ALL API calls
Auto-retry with exponential backoff (10s → 20s → 40s)
last_fetchedtracking to skip recently fetched accounts
Cost Estimates
Action | API Calls | Est. Cost |
Top 10 fetch | 10 | ~$0.015 |
Single account | 1 | ~$0.0015 |
Cache search | 0 | FREE |
Get opportunities | 0 | FREE |
Best Practices
Use
fetch_tweets(top_n=10)for daily routineUse
search_tweets(query, cache_only=True)to search cached dataLet
skip_recent_hoursprevent duplicate fetchesOnly do full fetches (
fetch_tweets()) when necessary
API Costs
twitterapi.io: ~$0.0015 per API call
Twitter API: Free tier (17 posts/day, 1,500/month cap)
Supabase: Free tier
License
MIT