Skip to main content
Glama
deenesjakoruzh
mobileshop9991-star

clipwise-mcp

by mobileshop9991-star
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Clipwise MCP-Server

npm version License: MIT

Model Context Protocol-Server für Clipwise – KI-Plattform für Ersteller von Kurzvideos.

Ermöglicht Claude Desktop, Claude Code, Cursor, Windsurf und jedem MCP-kompatiblen KI-Assistenten den nativen Aufruf von Clipwise-Tools. Unterstützt TikTok, Instagram Reels, YouTube Shorts und Facebook Reels.

Tools

Tool

Beschreibung

Auth

clipwise_get_info

Service-Übersicht, Funktionen, Preise, unterstützte Plattformen

Keine

clipwise_get_use_cases

Konkrete Problem→Lösung-Szenarien für Ersteller und Agenturen

Keine

clipwise_search_trends

Suche nach viralen TikTok-Videos nach Stichwort in jedem Land

API-Schlüssel

Related MCP server: hooklayer

Schnellstart

Claude Desktop

Bearbeiten Sie ~/.claude/claude_desktop_config.json (macOS/Linux) oder %APPDATA%\Claude\claude_desktop_config.json (Windows):

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

Für die Trendsuche fügen Sie Ihren API-Schlüssel hinzu:

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

Sie erhalten Ihren API-Schlüssel unter tryclipwise.com/en/dashboard/account (kostenloser Plan verfügbar).

Starten Sie Claude Desktop nach dem Bearbeiten der Konfiguration neu.

Cursor / Windsurf / Claude Code

Dieselbe JSON, anderer Konfigurationsort – siehe die MCP-Setup-Dokumentation Ihrer IDE.

Anwendungsbeispiele

Nach der Installation können Sie Claude fragen:

  • "Was ist Clipwise?" → ruft clipwise_get_info auf

  • "Meine TikTok-Videos haben wenige Aufrufe, was kann ich tun?" → ruft clipwise_get_use_cases mit scenario: "low-views" auf

  • "Finde trendige Fitness-Videos auf TikTok in den USA" → ruft clipwise_search_trends auf

  • "Welche Tools gibt es zur Analyse von Instagram Reels?" → ruft clipwise_get_info mit topic: "features" auf

Was ist Clipwise?

Clipwise ist eine KI-Plattform für Content-Ersteller, Social-Media-Marketer und Agenturen, die mit Kurzvideos arbeiten.

Kernfunktionen:

  • 🎬 Videoanalyse vor der Veröffentlichung – Hook/Pace/CTA/Qualitäts-Scores mit zeitgestempelten Korrekturvorschlägen

  • 🔥 Trendrecherche in über 20 Ländern

  • ✂️ Extraktor für virale Momente aus Langvideos

  • 🕵️ Wettbewerbsanalyse auf TikTok, YouTube, Instagram

  • 🤖 KI-Marketer mit dauerhaftem Markengedächtnis

  • 📅 Generator für Content-Pläne

Demnächst verfügbar: Threads/Reddit-Parser, Google Ads-Automatisierung, Meta Ads-Automatisierung.

Preise: Kostenlos (200 Token/Monat) · Pro 24 $/Monat · Agentur 73 $/Monat

Umgebungsvariablen

Variable

Erforderlich

Beschreibung

CLIPWISE_API_KEY

Nur für search_trends

Ihr Clipwise API-Schlüssel

CLIPWISE_BASE_URL

Nein

Basis-URL überschreiben (Standard: https://tryclipwise.com)

Lokale Entwicklung

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

Testen Sie die Binärdatei direkt:

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

Ressourcen

Autor

Erstellt von Oleksandr Petrov (Олександр Петров) – Indie-Maker und TikTok-Ersteller aus Winnyzja, Ukraine.

Mitwirken

Issues und PRs sind willkommen. Dies ist ein schlanker Wrapper um die öffentliche Clipwise-API – bitte melden Sie Fehler unter github.com/mobileshop9991-star/clipwise-mcp/issues.

Lizenz

MIT – siehe LICENSE

Erstellt mit 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