Skip to main content
Glama
deenesjakoruzh
mobileshop9991-star

clipwise-mcp

by mobileshop9991-star
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Clipwise MCPサーバー

npm version License: MIT

ショート動画クリエイター向けAIプラットフォームClipwiseのModel Context Protocolサーバー。

Claude Desktop、Claude Code、Cursor、Windsurf、およびMCP互換のAIアシスタントから、Clipwiseのツールをネイティブに呼び出せるようになります。TikTok、Instagram Reels、YouTube Shorts、Facebook Reelsに対応しています。

ツール

ツール

説明

認証

clipwise_get_info

サービスの概要、機能、料金、対応プラットフォーム

なし

clipwise_get_use_cases

クリエイターやエージェンシー向けの具体的な課題解決シナリオ

なし

clipwise_search_trends

国を指定してTikTokのバイラル動画をキーワード検索

APIキー

Related MCP server: hooklayer

クイックスタート

Claude Desktop

~/.claude/claude_desktop_config.json (macOS/Linux) または %APPDATA%\Claude\claude_desktop_config.json (Windows) を編集します：

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

トレンド検索を行うには、APIキーを追加してください：

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

APIキーはtryclipwise.com/en/dashboard/accountから取得できます（無料プランあり）。

設定ファイルを編集した後、Claude Desktopを再起動してください。

Cursor / Windsurf / Claude Code

JSONの内容は同じですが、設定ファイルの場所が異なります。各IDEのMCP設定ドキュメントを参照してください。

使用例

インストール後、Claudeに以下のように質問できます：

  • 「Clipwiseとは何ですか？」 → clipwise_get_infoを呼び出し

  • 「TikTok動画の再生数が伸びないのですが、どうすればいいですか？」 → scenario: "low-views"を指定してclipwise_get_use_casesを呼び出し

  • 「アメリカのTikTokでトレンドのフィットネス動画を探して」 → clipwise_search_trendsを呼び出し

  • 「Instagram Reelsを分析するためのツールには何がありますか？」 → topic: "features"を指定してclipwise_get_infoを呼び出し

Clipwiseとは？

Clipwiseは、ショート動画を扱うコンテンツクリエイター、ソーシャルメディアマーケター、エージェンシー向けのAIプラットフォームです。

主な機能：

  • 🎬 公開前の動画分析 — フック/ペース/CTA/品質スコアとタイムスタンプ付きの修正案

  • 🔥 20カ国以上のトレンド調査

  • ✂️ 長尺動画からのバイラルシーン抽出

  • 🕵️ TikTok、YouTube、Instagramの競合分析

  • 🤖 ブランドの記憶を保持するAIマーケター

  • 📅 コンテンツプラン生成

近日公開予定： Threads/Redditパーサー、Google広告自動化、Meta広告自動化。

料金： 無料（月200トークン） · Pro 月額24ドル · Agency 月額73ドル

環境変数

変数

必須

説明

CLIPWISE_API_KEY

search_trendsのみ

Clipwise APIキー

CLIPWISE_BASE_URL

いいえ

ベースURLの上書き（デフォルト: https://tryclipwise.com）

ローカル開発

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

バイナリを直接テストする：

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

リソース

作者

Oleksandr Petrov (Олександр Петров) が作成 — ウクライナのヴィーンヌィツャ出身のインディーメーカー兼TikTokクリエイター。

コントリビューション

IssueやPRを歓迎します。これは公開されているClipwise APIの薄いラッパーです。バグ報告はgithub.com/mobileshop9991-star/clipwise-mcp/issuesまでお願いします。

ライセンス

MIT — LICENSEを参照

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.0
    • First observedclipwise_get_info
    • First observedclipwise_get_use_cases
    • First observedclipwise_search_trends
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 3 tools

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
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers