mcp-seedance

Implements the Model Context Protocol (MCP) server specification to expose Seedance capabilities as a standardized interface that Claude and other MCP-compatible clients can discover and invoke. Uses MCP's resource, tool, and prompt registries to advertise available operations, handle bidirectional JSON-RPC communication, and manage request/response lifecycle with proper error handling and capability negotiation.

Exposes Seedance data entities (datasets, queries, reports, dashboards, or other domain objects) as MCP resources with URIs and content retrieval. Implements MCP's resource protocol to allow clients to discover available resources, read their content, and potentially subscribe to updates. Resources are mapped to Seedance API endpoints and cached or streamed based on size and freshness requirements.

Exposes Seedance operations (queries, transformations, exports, analyses) as MCP tools with JSON schema definitions. Implements MCP's tool calling protocol with schema validation, parameter marshalling, and result formatting. Tools are registered with descriptions and parameter schemas that allow MCP clients to understand what operations are available and invoke them with proper type checking.

Registers Seedance-specific prompt templates in the MCP prompts registry, allowing Claude and other clients to discover and use pre-built prompts for common Seedance tasks (data analysis, report generation, query optimization, etc.). Prompts are parameterized with variable substitution and can reference Seedance resources and tools to create complex workflows.

Manages authentication to Seedance API (API keys, OAuth tokens, or other credentials) at the MCP server level, handling credential storage, refresh, and injection into Seedance API calls. Implements secure credential handling patterns to prevent leaking credentials to MCP clients while maintaining proper authorization for Seedance operations.

Implements error handling for Seedance API failures, timeouts, and rate limiting, translating Seedance errors into MCP error responses with proper error codes and messages. Includes retry logic with exponential backoff for transient failures, circuit breaker patterns for cascading failures, and graceful degradation when Seedance is unavailable.

Implements caching layer for frequently accessed Seedance resources and query results to reduce API calls and latency. Uses TTL-based cache invalidation, LRU eviction policies, and optional distributed caching (Redis) for multi-instance deployments. Cache keys are based on resource URIs and query parameters to ensure correctness.