de en es ja ko ru zh

seedance-2-mcp

Name: seedance-2-mcp
Author: leonaiuv

by leonaiuv

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

seedance-2-mcp

npm version License: MIT

Ein Open-Source, lokal ausgeführter MCP (Model Context Protocol) Server, der die Videogenerierungsfunktionen von Volcengine ARK Seedance 2.0 über drei stdio-Tools für MCP-Clients wie Codex, Claude Desktop, Cursor usw. verfügbar macht.

Rein lokales stdio, keine Cloud-Bereitstellung erforderlich.
Geschrieben in Node.js + TypeScript, unter Verwendung des offiziellen @modelcontextprotocol/sdk.
Benutzer können Seedance 2.0 Text-zu-Video / Bild-zu-Video / multimodale Referenzgenerierung nutzen, indem sie einfach ihren ARK_API_KEY auf ihrem eigenen Rechner konfigurieren.

Verfügbare MCP Tools

Tool	Funktion
`seedance_usage_guide`	Gibt eine vollständige Anleitung zurück — Standardprozess, Modellauswahl, Parametertabelle, Hinweise.
`seedance_create_task`	Reicht einen Seedance 2.0 Videogenerierungsauftrag ein, gibt sofort `task_id` zurück, blockiert nicht.
`seedance_check_task`	Fragt den Status eines Auftrags mit `task_id` ab; bei Erfolg werden `video_url` und optional das letzte Frame-Bild zurückgegeben.

Details zu den Parametern finden Sie unter Tools im Detail.

Related MCP server: Seedance MCP

Schnelleinstieg für lokale Agents

Wenn Sie Codex, Claude Desktop, Cursor oder einen anderen MCP-fähigen lokalen Agenten verwenden, können Sie ihm den Link zu diesem Repository senden und ihn bitten, diesen Abschnitt zu lesen.

你是一个本地开发 Agent。请帮我把这个仓库提供的 seedance-2-mcp 接入到当前 MCP 客户端中。

目标：
1. 读取仓库 README，理解这是一个 stdio MCP server，用于调用火山方舟 Seedance 2.0 视频生成 API。
2. 优先使用 npx 方式接入：command = "npx"，args = ["-y", "seedance-2-mcp"]。
3. 如果 npm 包暂不可用，或我明确想从源码运行，请 clone 本仓库，执行 npm install && npm run build，并将 MCP command 配为 "node"，args 配为 ["<仓库绝对路径>/dist/index.js"]。
4. 只向我索要或确认 ARK_API_KEY，不要把真实 API Key 写进仓库、README、示例文件或 git。
5. 根据我当前使用的客户端自动修改对应 MCP 配置：
   - Codex：修改 ~/.codex/config.toml
   - Claude Desktop：修改 claude_desktop_config.json
   - Cursor 或其他客户端：使用它们支持的 stdio MCP 配置格式
6. 配置完成后，提醒我重启或刷新 MCP 客户端，然后先调用 seedance_usage_guide，再按 create -> wait -> check 的流程生成视频。
7. 如果本机没有 Node.js >= 18 或 npx 不可用，请先指出缺失项，并给出最小安装建议。

重要约束：
- stdout 是 MCP JSON-RPC 通道，不要让 server 在 stdout 打调试日志。
- ARK_API_KEY 只能放在 MCP 客户端 env 配置或本机环境变量里。
- 生成的 video_url 通常会过期，任务成功后应提示我尽快下载。

Sie können dem Agenten auch direkt sagen:

Lies dieses Repository und konfiguriere Seedance MCP für mich gemäß den „Schnelleinstieg für lokale Agents“ in der README. Ich werde den ARK_API_KEY bereitstellen.

Installation

1. Über `npx` (Empfohlen - keine manuelle Installation erforderlich)

Verwenden Sie dies direkt in der Konfiguration des MCP-Clients:

npx -y seedance-2-mcp

Bei jedem Start wird die neueste Version heruntergeladen (oder aus dem Cache verwendet).

2. Globale Installation

npm install -g seedance-2-mcp

Danach können Sie seedance-2-mcp in der Client-Konfiguration verwenden.

3. Aus dem Quellcode ausführen (für Entwickler)

git clone https://github.com/seedance/seedance-2-mcp.git
cd seedance-2-mcp
npm install
npm run build
node dist/index.js

Erfordert Node.js >= 18 (abhängig von nativem fetch).

Umgebungsvariablen

Variable	Erforderlich	Beschreibung
`ARK_API_KEY`	Ja	Volcengine ARK API Key. Besuchen Sie https://console.volcengine.com/ark zum Abrufen.
`ARK_BASE_URL`	Nein	Standard `https://ark.cn-beijing.volces.com/api/v3`. Kann für Übersee/Proxy überschrieben werden.

Kopieren Sie .env.example nach .env nur als Referenz für die Entwicklung; der tatsächlich wirksame Ort ist das env-Feld in der MCP-Client-Konfiguration, da der Client den MCP-Prozess als Kindprozess startet und die Umgebungsvariablen selbst injiziert.

Wenn ARK_API_KEY beim Aufruf eines Tools nicht gesetzt ist, geben die beiden Tools, die die echte API aufrufen, einen klaren Fehler zurück:

Missing ARK_API_KEY environment variable. Please set ARK_API_KEY to your Volcengine ARK API key.

Beispiel für Client-Konfiguration

Codex (`~/.codex/config.toml`)

[mcp_servers.seedance-2-mcp]
command = "npx"
args = ["-y", "seedance-2-mcp"]
env = { "ARK_API_KEY" = "your_key_here" }

Claude Desktop (`claude_desktop_config.json`)

macOS Pfad: ~/Library/Application Support/Claude/claude_desktop_config.json Windows Pfad: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "seedance-2-mcp": {
      "command": "npx",
      "args": ["-y", "seedance-2-mcp"],
      "env": {
        "ARK_API_KEY": "your_key_here"
      }
    }
  }
}

Cursor / Andere MCP-Clients

Allgemeine Konfiguration für jeden Client, der stdio MCP unterstützt:

{
  "command": "npx",
  "args": ["-y", "seedance-2-mcp"],
  "env": { "ARK_API_KEY": "your_key_here" }
}

Tools im Detail

`seedance_usage_guide`

Keine Parameter. Gibt eine vollständige Anleitung im Markdown-Format zurück. Es wird empfohlen, dies vor dem ersten Aufruf von seedance_create_task einmal aufzurufen.

`seedance_create_task`

Reicht einen Videogenerierungsauftrag ein, gibt sofort task_id zurück.

Eingabeparameter:

Feld	Typ	Standard	Beschreibung
`prompt`	string	— (erforderlich)	Beschreibung in natürlicher Sprache. Bei Referenzmaterialien im Prompt mit `[Image1]` / `[Video1]` / `[Audio1]` referenzieren.
`model`	enum	`doubao-seedance-2-0-260128`	`doubao-seedance-2-0-260128` (Standard, höchste Qualität) / `doubao-seedance-2-0-fast-260128` (Schnell).
`duration`	integer	`5`	Videodauer in Sekunden. `[4, 15]`.
`ratio`	enum	`16:9`	`21:9` / `16:9` / `4:3` / `1:1` / `3:4` / `9:16` / `adaptive`.
`resolution`	enum	`720p`	`480p` oder `720p`.
`generate_audio`	boolean	`true`	Ob synchrones Audio (Dialog / Soundeffekte / BGM) mitgeneriert werden soll.
`watermark`	boolean	`true`	Ob ein Plattform-Wasserzeichen hinzugefügt werden soll. Manche Konten können dies möglicherweise nicht deaktivieren.
`web_search`	boolean	`false`	Ob die Web-Suche für den Prompt aktiviert werden soll; nur bei reinem Texteingang verfügbar, kann nicht gleichzeitig mit image/video/audio verwendet werden.
`return_last_frame`	boolean	`false`	Ob die URL des letzten Frames für das Spleißen von Segmenten zurückgegeben werden soll.
`image_urls`	array	—	Maximal 9 Elemente; jedes `{ url, role? }`, `role` ∈ `reference_image` / `first_frame` / `last_frame`, Standard `reference_image`.
`video_urls`	array	—	Maximal 3 Elemente; jedes `{ url, role? }`, `role` ∈ `reference_video`.
`audio_urls`	array	—	Maximal 3 Elemente; jedes `{ url, role? }`, `role` ∈ `reference_audio`. Muss mit image oder video kombiniert werden.

Validierungsregeln:

duration muss eine Ganzzahl zwischen [4, 15] sein.
image_urls ≤ 9, video_urls ≤ 3, audio_urls ≤ 3.
Nur reiner Text + audio_urls wird abgelehnt (Seedance unterstützt dies nicht).
web_search=true zusammen mit Referenzmaterial wird abgelehnt (Web-Suche unterstützt nur reinen Text).

Rückgabe:

{
  "task_id": "cgt-2026xxxx-xxxxxx",
  "model": "doubao-seedance-2-0-260128",
  "duration": 5,
  "ratio": "16:9",
  "resolution": "720p",
  "raw": { /* 火山原始响应 */ }
}

`seedance_check_task`

Eingabe { task_id: string }. Mögliche Status:

running / queued / pending — Wird noch verarbeitet. Bitte 30-90 Sekunden warten und erneut aufrufen.
succeeded — Gibt video_url zurück; falls return_last_frame=true, wird auch last_frame_url zurückgegeben.
failed — Gibt fail_reason zurück (falls vorhanden).
cancelled / expired — Auftrag wurde abgebrochen oder ist abgelaufen.
Andere — Gibt status und das ursprüngliche Payload unverändert zurück.

Typischer Aufrufablauf

client → seedance_usage_guide                                  ← 阅读规则
client → seedance_create_task { prompt, ... }                  ← 提交任务
                                                ↓
                                        task_id: cgt-...
                                                ↓
client → seedance_check_task { task_id }                       ← 30-90s 后轮询
                                ↓
                        status: running         （继续等待）
                                ↓
                        status: succeeded       ← 返回 video_url
                                ↓
                立刻下载 video_url（约 24h 内会过期）

Ein 15-Sekunden-Auftrag mit dem Standardmodell benötigt normalerweise 2-5 Minuten; die schnelle Version ist kürzer.

Sicherheitshinweise

Schreiben Sie den ARK_API_KEY nicht in das git-Repository. Platzieren Sie ihn im env-Feld der MCP-Client-Konfiguration (z. B. claude_desktop_config.json, ~/.codex/config.toml) oder in den Shell-Umgebungsvariablen.
Dieses Tool druckt den ARK_API_KEY nicht in Protokollen oder Rückgabewerten.
Die von Volcengine generierten video_url und last_frame_url sind signierte temporäre URLs, die laut offiziellen Angaben von Volcengine standardmäßig 24 Stunden gültig sind; bitte laden Sie die Dateien nach erfolgreichem Auftrag zeitnah herunter, um ein Ablaufen der Links zu vermeiden.
Die von Ihnen übergebenen image_urls / video_urls / audio_urls müssen öffentlich zugängliche HTTPS- (oder HTTP-) Adressen sein; lokale Pfade, interne Netzwerkadressen oder Ressourcen, die einen Login erfordern, können vom Volcengine-Server nicht abgerufen werden.
Bitte halten Sie sich an die Nutzungsbedingungen von Volcengine ARK und dem Seedance-Modell und generieren Sie keine illegalen, jugendgefährdenden oder urheberrechtsverletzenden Inhalte.

Entwicklung

npm install
npm run typecheck
npm run dev          # 用 tsx 直接跑 src/index.ts
npm run build        # 输出到 dist/
npm start            # node dist/index.js

Empfehlung für das Debugging von stdio MCP:

npx -y @modelcontextprotocol/inspector npx -y seedance-2-mcp

Oder lokaler Quellcode:

npx -y @modelcontextprotocol/inspector node dist/index.js

Projektstruktur

.
├── src/
│   ├── index.ts          # stdio MCP 入口（带 shebang）
│   ├── server.ts         # 注册 McpServer 和三个 tools
│   ├── seedance.ts       # 火山方舟 Seedance 2.0 REST API 客户端
│   ├── schema.ts         # zod 输入 schema
│   └── usageGuide.ts     # seedance_usage_guide 返回的文本
├── package.json
├── tsconfig.json
├── .env.example
├── .gitignore
├── LICENSE
└── README.md

Lizenz

MIT © seedance-2-mcp contributors

Dieses Projekt hat keine offizielle Verbindung zu ByteDance, Volcengine oder Volcengine ARK. Die Namen "Seedance", "Doubao", "火山方舟" usw. sind Eigentum ihrer jeweiligen Inhaber.

Available Tools

3 tools

seedance_check_taskCheck Seedance 2.0 task statusA

Read-onlyIdempotent

Query the status of a Seedance 2.0 task by task_id. Returns running / succeeded / failed / other. On success returns video_url (and last_frame_url if return_last_frame was true). Generated URLs expire within ~24h - download promptly.

ParametersJSON Schema

Name	Required	Description	Default
`task_id`	Yes	Seedance task id returned by seedance_create_task (e.g. cgt-...).

TDQS

A4.2/5.0

Behavior4/5

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

Annotations indicate readOnly and idempotent. Description adds URL expiration (~24h) and return format, which isn't in annotations. No contradiction.

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?

Three sentences, front-loaded with purpose, no redundant or extraneous content. Efficient and clear.

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?

Describes statuses and URL expiry without output schema. Adequate for a status check tool; could mention error handling but not required.

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

Parameters4/5

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

Schema has 100% coverage with description for task_id. Description adds context that it's the ID from seedance_create_task, improving usability.

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 it queries status of a Seedance 2.0 task by task_id, lists possible statuses and success returns. Distinguishes from sibling tools (create and guide).

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

Usage Guidelines3/5

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

Implies usage after task creation but does not explicitly state when to use vs alternatives or mention polling patterns. No when-not or alternatives provided.

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

seedance_create_taskCreate Seedance 2.0 video generation taskA

Submit a Seedance 2.0 video generation task to the Volcengine ARK API and return the task_id immediately. Does NOT wait for the video to render - poll seedance_check_task afterwards. Reference media URLs must be publicly reachable.

ParametersJSON Schema

Name	Required	Description	Default
`prompt`	Yes	Natural-language description of the desired video. Reference images / videos / audios with [Image1], [Video1], [Audio1] in 1-based order if you provided any.
`model`	No	Seedance 2.0 model id. doubao-seedance-2-0-260128 is the standard, highest-quality model. doubao-seedance-2-0-fast-260128 trades quality for latency.	doubao-seedance-2-0-260128
`duration`	No	Video length in seconds. Must be an integer in [4, 15].
`ratio`	No	Aspect ratio. Use 9:16 for vertical short-video, 16:9 for landscape. 'adaptive' lets the model pick the best fit when reference media is provided.	16:9
`resolution`	No	Output resolution. 720p is recommended; 480p is faster/cheaper.	720p
`generate_audio`	No	Whether to generate synchronized audio (dialogue, SFX, music). Set false for silent video.
`watermark`	No	Whether to add the platform watermark. Some accounts cannot disable this.
`web_search`	No	Enable prompt enhancement via web search. Text-only input is required when this is true.
`return_last_frame`	No	Return the last frame as an image URL alongside the video URL. Useful for chaining segments.
`image_urls`	No	Up to 9 reference images. Each item is { url, role? }. role defaults to 'reference_image'. Use 'first_frame' (and optionally 'last_frame') for image-to-video animation.
`video_urls`	No	Up to 3 reference videos. Each item is { url, role? }. role defaults to 'reference_video'.
`audio_urls`	No	Up to 3 reference audios. Each item is { url, role? }. role defaults to 'reference_audio'. Audio MUST be paired with at least one image or video reference.

TDQS

A4.6/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=false, and the description confirms a mutation (creates a task). It adds context beyond annotations: the async nature ('Does NOT wait for the video to render') and the requirement for public URLs. However, it does not mention rate limits, error handling, or response structure.

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?

Three sentences containing no fluff: first states core function, second explains async behavior with action, third adds constraint. Front-loaded with the most important information.

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?

For a tool with 12 parameters and no output schema, the description covers the essential workflow and a key constraint (public URLs). It lacks details on error cases or the exact format of the returned task_id, but the async instruction is clear. Overall adequate but could be slightly more detailed.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value beyond schema by emphasizing the async behavior and public URL requirement, which are not evident from individual parameter descriptions. It also clarifies the workflow (submit then poll).

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?

The description clearly states the verb 'Submit' and the resource 'Seedance 2.0 video generation task'. It specifies that it returns a task_id immediately and does not wait for rendering, distinguishing it from sibling tools like seedance_check_task that are used for polling.

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

Usage Guidelines5/5

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

The description explicitly instructs to poll seedance_check_task afterwards and notes that reference media URLs must be publicly reachable. It provides clear guidance on when to use this tool (to initiate a task) and what to do next (poll for results).

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

seedance_usage_guideSeedance 2.0 usage guideA

Read-onlyIdempotent

Returns the canonical usage guide for the Seedance 2.0 MCP: standard create -> wait -> check workflow, model choices, parameter reference, and important caveats. Call this before your first seedance_create_task.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.3/5.0

Behavior3/5

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

Annotations (readOnlyHint, idempotentHint) already declare safe, idempotent behavior. The description adds that it returns a guide, but no additional behavioral traits beyond what annotations provide.

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 sentences, no wasted words. Front-loaded with key purpose and usage instruction. Highly concise and well-structured.

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?

For a zero-parameter, no-output-schema guide tool, the description fully explains its purpose, content, and when to use it. No gaps.

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

Parameters4/5

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

No parameters exist, so baseline is 4. The description adds meaning by explaining the tool's purpose and content, compensating for lack of parameters.

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?

The description clearly states it returns the canonical usage guide for Seedance 2.0 MCP, detailing workflow, model choices, parameters, and caveats. It distinguishes itself from sibling tools (check, create) by being the preliminary guide.

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?

Explicit advice to call before first seedance_create_task provides clear context for use. No exclusions or alternatives are needed given its unique role as a guide.

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.

3 tool updatesv0.1.0May 2, 2026
- First observedseedance_check_task
- First observedseedance_create_task
- First observedseedance_usage_guide

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.4/5.0

Scored 2026-05-02 19:30 across 3 tools

Disambiguation5/5

Each tool has a unique and clear purpose: creating a task, checking its status, and providing usage instructions. There is no overlap in functionality.

Naming Consistency4/5

All tools share the 'seedance_' prefix and follow a noun-based pattern (check_task, create_task, usage_guide), but 'usage_guide' is not a verb_noun like the others, causing minor inconsistency.

Tool Count5/5

With only 3 tools, the set is tightly scoped to the core workflow of generating and monitoring a video task, plus a guide. This is appropriate for the narrow domain.

Completeness4/5

The tools cover the essential create-and-check workflow, and the guide complements them. However, missing operations like task cancellation or listing are minor gaps but not critical for the basic use case.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

mcp-seedanceOAuth
io.github.AceDataCloud
MCP server for ByteDance Seedance AI video generation
Image & Video Processing Multimedia Processing Entertainment & Media
220
StoryStudioOAuth
io.github.HelloElo-Fr
AI image, video, voice and music generation over MCP, routed to Veo 3.1, Seedance 2.5 and more.
AI & Machine Learning Image & Video Processing Audio Processing
1
Treza A
io.github.treza-labs
Build, run, schedule, and publish AI video pipelines to YouTube and TikTok from any MCP client.
AI & Machine Learning Image & Video Processing Payments & Billing
241
mcp-veoOAuth
io.github.AceDataCloud
MCP server for Google Veo AI video generation
Multimedia Processing Image & Video Processing Entertainment & Media
23

Related MCP Servers

Seedream/Seedance MCP Server
nsmao-com
A
license
C
quality
D
maintenance
Integrates Volcengine's Ark API to provide image and video generation and editing capabilities. It supports both local stdio and remote HTTP transport modes for flexible deployment and use.
Updated 7 months ago (2026-03-05 14:24 UTC)
8
24 npm
3
MIT
Seedance MCP
AI & Machine Learning Multimedia Processing Image & Video Processing
dpspace2050
F
license
A
quality
D
maintenance
Enables video generation using the Seedance 2.0 model through MCP, supporting both OpenAI and Volcengine API formats with tools for creating, monitoring, and downloading videos.
Updated 4 months ago (2026-06-12 11:12 UTC)
6
-
MathMind MCP Server
Multimedia Processing Image & Video Processing Audio Processing
Runninghcm
F
license
A
quality
D
maintenance
Provides a audio/video creation toolbox via MCP protocol, enabling natural language-based video editing tasks such as image-to-video, video merging, subtitle extraction, and more.
Updated a year ago (2025-08-09 17:53 UTC)
9
3
-
Seedance 2.5 MCP Server
AI & Machine Learning Image & Video Processing
Anil-matcha
A
license
Not graded
quality
B
maintenance
MCP server for generating Seedance 2.5 videos via MuAPI, enabling text-to-video, image-to-video, first/last frame, and omni reference workflows with 720p/480p resolution selection.
Updated 10 days ago (2026-09-28 12:58 UTC)
7
MIT

seedance-2-mcp

Verfügbare MCP Tools

Schnelleinstieg für lokale Agents

Installation

1. Über npx (Empfohlen - keine manuelle Installation erforderlich)

2. Globale Installation

3. Aus dem Quellcode ausführen (für Entwickler)

Umgebungsvariablen

Beispiel für Client-Konfiguration

Codex (~/.codex/config.toml)

Claude Desktop (claude_desktop_config.json)

Cursor / Andere MCP-Clients

Tools im Detail

seedance_usage_guide

seedance_create_task

seedance_check_task

Typischer Aufrufablauf

Sicherheitshinweise

Entwicklung

Projektstruktur

Lizenz

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

1. Über `npx` (Empfohlen - keine manuelle Installation erforderlich)

Codex (`~/.codex/config.toml`)

Claude Desktop (`claude_desktop_config.json`)

`seedance_usage_guide`

`seedance_create_task`

`seedance_check_task`