Skip to main content
Two ways to give your AI coding agent Decart expertise: skills teach it API patterns upfront, and the MCP server lets it search Decart’s documentation on demand. Use both for best results.

​
Agent skill

A skill is a static knowledge file your agent loads at startup. It teaches the agent which API to use, how to authenticate, which models to pick, and what mistakes to avoid.
1

Install the Decart skill

Run this in your project directory:
npx skills add https://docs.platform.decart.ai
The CLI auto-discovers the skill and installs it to your detected coding agents.
2

Start building

Your agent now has context about Decart’s Realtime, Queue, and Process APIs. Try asking it:
  • “Add live camera effects using Decart’s realtime API”
  • “Generate a video from a text prompt using Decart”
  • “Create a talking avatar that lip-syncs to audio”
Your agent learnsDetails
API selectionWhich API (Realtime, Queue, Process) fits your use case
Model selectionWhich model for character transform, style transfer, video gen, image gen
AuthenticationServer-side API keys vs client-side token generation
SDK patternsCorrect code patterns for JavaScript and Python
Common mistakesCamera resolution, API key exposure, cleanup, moderation handling
npx skills add https://docs.platform.decart.ai -a claude-code
npx skills add https://docs.platform.decart.ai -a cursor

npx skills add https://docs.platform.decart.ai -g
Skills work with 30+ coding agents including Claude Code, Cursor, GitHub Copilot, Windsurf, and OpenCode. See the full list.

​
MCP server

The MCP (Model Context Protocol) server gives your agent a live search tool that queries Decart documentation on demand. Unlike the skill which is loaded once, MCP lets the agent look up specific details — exact parameters, migration guides, changelog entries — as it works. Add the Decart MCP server to your agent: 
claude mcp add decart-docs https://docs.platform.decart.ai/mcp --transport http
Once connected, your agent can search Decart documentation automatically while generating responses — no need to ask it explicitly.

​
Skill vs MCP

SkillMCP
How it worksPre-loaded context at startupLive search during conversation
Best forAPI patterns, model selection, gotchasExact parameters, examples, latest changes
Setupnpx skills add (one time)Add MCP config (one time)
Token costLoaded once (~200 lines)Per-search, only what’s needed
Use both together. The skill gives your agent the big picture so it picks the right API and model. The MCP server fills in specifics when the agent needs exact parameter details or code examples.

​
Prompting tips

Get better results from your agent by being specific about what you’re building:
  • Name the API — “Use the Realtime API” or “Use the Queue API” instead of just “use Decart”
  • Specify the model — “Use lucy_2_rt for character transform” rather than letting the agent guess
  • Mention the SDK — “Using the JavaScript SDK” or “Using Python” so it generates the right syntax
  • Ask for client tokens — “Make sure to use client tokens for the browser code” for frontend work
  • Reference the platform — “Check the Decart docs for the exact parameters” triggers the MCP search