Clipwise MCP vs Social → Context
A side-by-side look at the Clipwise MCP and Social → Context 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 Social → Context for social media over a hosted endpoint. 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 Social → Context when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
socialdl_extract, socialdl_metadata, socialdl_download.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 61/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | CLIPWISE_API_KEYCLIPWISE_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 9 |
| Full listing | View Clipwise MCP | View Social → Context |
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.
Social → Context tools 9
socialdl_extractDownload a social-media link (TikTok, Instagram reel/post/carousel, YouTube, or any direct .mp4) and return it as usable text context: metadata (author, caption, duration), the audio/video transcript, and a vision description (OCR + summary) of each image in a carousel/post. YouTube uses its existing captions when available. Use this to give Claude the content of a video or post the user pasted.socialdl_metadataLightweight lookup: resolve a social-media link to its metadata (author, caption, duration, counts) and media URLs WITHOUT transcribing or running vision. Cheaper than socialdl_extract — use when the caption/context alone is enough.socialdl_downloadResolve a TikTok / Instagram / YouTube link (or direct .mp4/image URL) to its DIRECT download URLs from the source CDN — every video quality, audio track and image, with quality labels. Use when the user wants to DOWNLOAD/save the media instead of transcribing it. No transcription/vision.show_versionShow the current MCP platform and adapter versions.report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
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"
}
}
}
}
Social → Context
{
"mcpServers": {
"social-context": {
"url": "https://api.mcp.ai/p_socialdl"
}
}
}
Frequently asked questions
Clipwise MCP is categorized under Social Media and uses a local stdio subprocess. Social → Context belongs to Social Media and uses a remote HTTP/SSE transport. Pick Clipwise MCP for social media work and Social → Context 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. Social → Context 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 social-context 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. Social → Context has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.