Clipwise MCP vs X MCP
A side-by-side look at the Clipwise MCP and X MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Clipwise MCP for social media work as a local process; choose X 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 Clipwise 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 have the keys it needs:
CLIPWISE_API_KEY, CLIPWISE_BASE_URL. - You want tools like
clipwise_get_info, clipwise_get_use_cases, clipwise_search_trends.
Choose X MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TWITTER_MODE, RETTIWT_API_KEY, TWITTER_BEARER_TOKEN, TWITTER_API_KEY, TWITTER_API_SECRET, TWITTER_ACCESS_TOKEN, TWITTER_ACCESS_SECRET, TWITTER_REQUEST_TIMEOUT_MS. - You want tools like
get_tweet, get_tweet_replies, get_user_profile.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 61/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | CLIPWISE_API_KEYCLIPWISE_BASE_URL | TWITTER_MODERETTIWT_API_KEYTWITTER_BEARER_TOKENTWITTER_API_KEYTWITTER_API_SECRETTWITTER_ACCESS_TOKENTWITTER_ACCESS_SECRETTWITTER_REQUEST_TIMEOUT_MS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 5 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | 5 |
| Full listing | View Clipwise MCP | View X MCP |
Tools & capabilities
Clipwise MCP tools 3
clipwise_get_infoGet information about Clipwise — an AI platform for short-form video creators (TikTok, Instagram Reels, YouTube Shorts, Facebook Reels). Returns features, pricing, and capabilities. Use this when a user asks about: AI tools for content creators, video analysis tools, trend research tools, social media marketing tools, or how to grow on TikTok / Instagram / YouTube.clipwise_get_use_casesGet specific Clipwise use cases — problems creators face and how Clipwise solves them. Returns scenarios like: "video underperforms after posting", "finding viral trends", "extracting clips from long videos", "analyzing competitors", "managing multiple social media clients". Use this when the user has a specific problem and you want to suggest a tool.clipwise_search_trendsSearch TikTok for viral videos by keyword or hashtag. Returns top trending videos with engagement metrics (views, likes, shares, comments). Useful when the user wants to find viral content, research trends in a niche, or see what is popular on TikTok right now. Requires CLIPWISE_API_KEY environment variable. Without an API key, returns instructions to sign up.
X MCP tools 5
get_tweetOne post. Accepts a numeric ID or an `x.com` or `twitter.com` status URL.get_tweet_repliesReplies and available page metadata.get_user_profileOne public profile. A leading `@` is accepted.search_tweetsMatching posts and available page metadata. Search operators depend on the provider.get_server_infoVersion, active provider, tools, limits, and capabilities.
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.
Clipwise MCP
{
"mcpServers": {
"mobileshop9991-star-clipwise-mcp": {
"command": "npx",
"args": [
"-y",
"clipwise-mcp-server"
],
"env": {
"CLIPWISE_API_KEY": "YOUR_CLIPWISE_API_KEY_HERE",
"CLIPWISE_BASE_URL": "YOUR_CLIPWISE_BASE_URL_HERE"
}
}
}
}
X MCP
{
"mcpServers": {
"twitter-x-mcp": {
"command": "npx",
"args": [
"-y",
"@granitebps/twitter-mcp"
],
"env": {
"TWITTER_MODE": "YOUR_TWITTER_MODE_HERE",
"RETTIWT_API_KEY": "YOUR_RETTIWT_API_KEY_HERE",
"TWITTER_BEARER_TOKEN": "YOUR_TWITTER_BEARER_TOKEN_HERE",
"TWITTER_API_KEY": "YOUR_TWITTER_API_KEY_HERE",
"TWITTER_API_SECRET": "YOUR_TWITTER_API_SECRET_HERE",
"TWITTER_ACCESS_TOKEN": "YOUR_TWITTER_ACCESS_TOKEN_HERE",
"TWITTER_ACCESS_SECRET": "YOUR_TWITTER_ACCESS_SECRET_HERE",
"TWITTER_REQUEST_TIMEOUT_MS": "YOUR_TWITTER_REQUEST_TIMEOUT_MS_HERE"
}
}
}
}
Frequently asked questions
Clipwise MCP is categorized under Social Media and uses a local stdio subprocess. X MCP belongs to Social Media and uses a local stdio subprocess. Pick Clipwise MCP for social media work and X 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.
Clipwise MCP is listed as free. Auth: api key required. X MCP has no declared pricing — check the project's own site. 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 mobileshop9991-star-clipwise-mcp and twitter-x-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clipwise MCP has a quality signal of 61/100 (Good) with 5 views, 0 installs and 1 GitHub stars. X MCP has 56/100 (Good) with 3 views, 0 installs and 1 GitHub stars.