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용 모델 컨텍스트 프로토콜(MCP) 서버입니다.

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"
      }
    }
  }
}

tryclipwise.com/en/dashboard/account에서 API 키를 받으세요(무료 플랜 이용 가능).

설정 파일을 편집한 후 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 Ads 자동화, Meta Ads 자동화.

가격: 무료(월 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

리소스

작성자

우크라이나 빈니차 출신의 인디 메이커이자 TikTok 크리에이터인 Oleksandr Petrov(Олександр Петров)가 제작했습니다.

기여

이슈 및 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