TwitterAPIs vs Veezee MCP
A side-by-side look at the TwitterAPIs and Veezee MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose TwitterAPIs for social media work as a local process; choose Veezee MCP for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose TwitterAPIs when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TWITTERAPIS_KEY. - You want tools like
twitter_advanced_search, twitter_user_search, twitter_user_info.
Choose Veezee MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
linkedin_resolve_url, linkedin_get_profile, linkedin_search_people.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 56/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | TWITTERAPIS_KEY | None listed |
Tools & capabilities
TwitterAPIs tools 80
twitter_advanced_searchSearch tweets with X operators (`from:`, `min_faves:`, `since:`, `filter:links`, etc.)twitter_user_searchFind user accounts by name or keywordtwitter_user_infoFull profile by handle (bio, counts, verification, location)twitter_user_info_by_idFull profile by numeric user idtwitter_user_statusIs an account alive, suspended, or deletedtwitter_user_aboutA user's structured About object (category, professional/business labels, verification + identity-verification flags, joined date, and X's 'About this account' transparency panel)twitter_user_about_batchThe same About object for up to 100 accounts in one call (usernames or user_ids), billed per account answered; for vetting a list by country or account historytwitter_audience_summaryWho an audience is: a country histogram and likely-bot share over a sample of up to 100 followers or retweeterstwitter_user_affiliatesAccounts affiliated with an organization profiletwitter_check_follow_relationshipFollow relationship between two accounts, by id or username (who follows whom)twitter_check_follow_relationship_batchOne account against up to 100 others in one call, either direction (which of these accounts follow the brand)twitter_user_tweetsA user's recent original tweets (replies excluded)- +68 more on the listing page
Veezee MCP tools
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
TwitterAPIs
{
"mcpServers": {
"twitterapis": {
"command": "npx",
"args": [
"-y",
"@twitterapis/mcp@latest"
],
"env": {
"TWITTERAPIS_KEY": "YOUR_TWITTERAPIS_KEY_HERE"
}
}
}
}
Veezee MCP
{
"mcpServers": {
"veezeehq-veezee-mcp": {
"command": "npx",
"args": [
"-y",
"github:veezeehq/veezee-mcp"
]
}
}
}
Frequently asked questions
TwitterAPIs is categorized under Social Media and uses a local stdio subprocess. Veezee MCP belongs to Social Media and uses a local stdio subprocess. Pick TwitterAPIs for social media work and Veezee MCP for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
TwitterAPIs has no declared pricing — check the project's own site. Veezee MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add twitterapis and veezeehq-veezee-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TwitterAPIs has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Veezee MCP has 57/100 (Good) with 4 views, 0 installs and 0 GitHub stars.