Skip to main content
Glama
deenesjakoruzh
mobileshop9991-star

clipwise-mcp

by mobileshop9991-star
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Clipwise MCP Server

npm version License: MIT

Model Context Protocol server for Clipwise — AI platform for short-form video creators.

Lets Claude Desktop, Claude Code, Cursor, Windsurf, and any MCP-compatible AI assistant call Clipwise tools natively. Covers TikTok, Instagram Reels, YouTube Shorts, and Facebook Reels.

Tools

Tool

Description

Auth

clipwise_get_info

Service overview, features, pricing, supported platforms

None

clipwise_get_use_cases

Concrete problem→solution scenarios for creators and agencies

None

clipwise_search_trends

Search viral TikTok videos by keyword in any country

API key

Related MCP server: SEO Content Autopilot by Citedy

Quick Start

Claude Desktop

Edit ~/.claude/claude_desktop_config.json (macOS/Linux) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "clipwise": {
      "command": "npx",
      "args": ["-y", "clipwise-mcp-server"]
    }
  }
}

For trend search, add your API key:

{
  "mcpServers": {
    "clipwise": {
      "command": "npx",
      "args": ["-y", "clipwise-mcp-server"],
      "env": {
        "CLIPWISE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Get your API key at tryclipwise.com/en/dashboard/account (free plan available).

Restart Claude Desktop after editing the config.

Cursor / Windsurf / Claude Code

Same JSON, different config location — see your IDE's MCP setup docs.

Usage Examples

Once installed, you can ask Claude:

  • "What is Clipwise?" → calls clipwise_get_info

  • "My TikTok videos get low views, what can I do?" → calls clipwise_get_use_cases with scenario: "low-views"

  • "Find trending fitness videos on TikTok in the US" → calls clipwise_search_trends

  • "What tools exist for analyzing Instagram Reels?" → calls clipwise_get_info with topic: "features"

What is Clipwise?

Clipwise is an AI platform for content creators, social media marketers, and agencies who work with short-form video.

Core features:

  • 🎬 Pre-publish video analysis — Hook/Pace/CTA/Quality scores with timestamped fixes

  • 🔥 Trend research across 20+ countries

  • ✂️ Viral moments extractor for long-form video

  • 🕵️ Competitor analysis on TikTok, YouTube, Instagram

  • 🤖 AI Marketer with persistent brand memory

  • 📅 Content plan generator

Coming soon: Threads/Reddit parser, Google Ads automation, Meta Ads automation.

Unlike basic AI wrappers, Clipwise uses a knowledge-base architecture — 35+ curated playbooks (hook psychology, script structures, platform benchmarks, copywriting formulas, humanizer rules) are injected into every AI call. Scripts pass through an AI-writing detection layer so output sounds human, not like ChatGPT.

Pricing: Free (200 tokens/mo) · Pro $24/mo · Agency $73/mo

Environment Variables

Variable

Required

Description

CLIPWISE_API_KEY

For search_trends only

Your Clipwise API key

CLIPWISE_BASE_URL

No

Override base URL (default: https://tryclipwise.com)

Local Development

git clone https://github.com/mobileshop9991-star/clipwise-mcp.git
cd clipwise-mcp
npm install
npm run build
node dist/index.js

Test the binary directly:

echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | node dist/index.js

Resources

Author

Created by Oleksandr Petrov (Олександр Петров) — indie maker and TikTok creator from Vinnytsia, Ukraine.

Contributing

Issues and PRs welcome. This is a thin wrapper around the public Clipwise API — please report bugs at github.com/mobileshop9991-star/clipwise-mcp/issues.

License

MIT — see LICENSE

Built with Model Context Protocol · Anthropic SDK

Available Tools

3 tools
clipwise_get_infoA

Get 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
topicNoWhat to get info about: "overview", "features", "pricing", or "platforms"overview

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description must disclose behavior. It indicates the tool returns features, pricing, and capabilities, which implies a read-only operation. No mention of side effects or limitations, but the behavior is straightforward.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with no filler. Front-loaded with purpose, then specific usage guidance. Every word is necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single optional parameter and no output schema, the description is adequate. It covers the tool's purpose and when to use it. Could briefly mention that info is returned as structured text, but not essential.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers 100% of parameters with descriptions and enums. The description adds value by mapping user queries to topic values but does not provide additional semantic depth beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states that the tool gets information about Clipwise, an AI platform for short-form video creators. Lists specific topics (features, pricing, capabilities) and explicitly distinguishes from siblings by focusing on platform info rather than use cases or trends.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use: 'Use this when a user asks about: ...' with a list of common queries. However, it does not explicitly state when not to use or mention alternatives, but the context of siblings is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

clipwise_get_use_casesA

Get 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
scenarioNoSpecific scenario: "low-views", "trend-research", "long-video-clipping", "competitor-analysis", "agency-management", "content-strategy", or "all"all

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but description indicates a read-only query returning scenarios. Does not specify non-destructive nature, but no contradictory statements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded purpose, no extraneous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a simple tool with one well-documented parameter and no output schema. Agent can understand function and usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with full enum and default. Description only adds examples, not additional semantics beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it retrieves specific Clipwise use cases, listing concrete examples. Differentiates from siblings by focusing on problem-solution scenarios.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises using when user has a specific problem to suggest a tool. Lacks explicit when-not-to-use or comparison to siblings, but guidance is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: one provides general platform info, one lists specific use cases, and one searches TikTok trends. No overlap in functionality.

Naming Consistency5/5

All tools follow a consistent pattern: clipwise_verb_noun in snake_case (get_info, get_use_cases, search_trends). No deviations.

Tool Count4/5

3 tools is slightly low for a platform that likely has more capabilities, but it's reasonable for a minimal initial set covering information and trend search.

Completeness3/5

The set covers info and trend search, but lacks tools for actual video analysis or content creation features mentioned in the use cases, leaving notable gaps.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mobileshop9991-star/clipwise-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server