Twitter Signal MCP vs Clipwise MCP

A side-by-side look at the Twitter Signal MCP and Clipwise MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Twitter Signal MCP logoTwitter Signal MCPSocial Media · Local subprocess (stdio)Live X/Twitter search and AI trend digests. No Twitter API key — pay per call in USDC via x402.44FairAuth: not declaredClipwise MCP logoClipwise MCPSocial Media · Local subprocess (stdio)AI platform for short-form video creators (TikTok, Instagram Reels, YouTube Shorts, Facebook Reels). Three tools — viral TikTok trend search across 20+ countries, service info, and use-case scenarios for video analysis, competitor research, and content strategy. Install: npx -y clipwise-mcp-server. Free plan at tryclipwise.com.61GoodAuth: api key required

Verdict: choose Twitter Signal MCP for social media work as a local process; choose Clipwise 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?

Twitter Signal MCP logoChoose Twitter Signal MCP when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
Explore Twitter Signal MCP

Clipwise MCP logoChoose 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.
Explore Clipwise MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTwitter Signal MCP logoTwitter Signal MCPClipwise MCP logoClipwise MCP
CategorySocial MediaSocial Media
Quality signal44/100 · Fair61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsNone listedCLIPWISE_API_KEYCLIPWISE_BASE_URL
Verified ownerCommunity listingCommunity listing
GitHub stars11
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listed3

Tools & capabilities

Twitter Signal MCP tools

No tool names declared yet. Check the project README from the listing page.

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.

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.

Twitter Signal MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "twitter-signal-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "twitter-signal-mcp"
      ]
    }
  }
}

Clipwise MCP

mcpServers (Claude Desktop / Cursor)
{
  "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"
      }
    }
  }
}

Frequently asked questions

Twitter Signal MCP is categorized under Social Media and uses a local stdio subprocess. Clipwise MCP belongs to Social Media and uses a local stdio subprocess. Pick Twitter Signal MCP for social media work and Clipwise 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.

Twitter Signal MCP has no declared pricing — check the project's own site. Clipwise MCP is listed as free. 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 twitter-signal-mcp and mobileshop9991-star-clipwise-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Twitter Signal MCP has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Clipwise MCP has 61/100 (Good) with 5 views, 0 installs and 1 GitHub stars.