List the templates first every time — the layer names a template exposes are exactly the keys you pass in, and guessing them is the usual reason a render comes back wrong. Long video renders return a job ID rather than a URL, so pick it up in the Placid dashboard instead of waiting on the tool call.
A small server over the Placid.app API for creative automation: list the templates in your account, then render one by supplying content for its layers.
- placid_list_templates returns your templates with title, UUID, preview thumbnail, the layers each one exposes with their types, and tags — filterable by collection, tags or custom reference data
- placid_generate_image fills a template's text and image layers and returns a URL to the finished image
- placid_generate_video fills video, image and text layers and returns a video URL, or a job ID to follow in the Placid dashboard when the render runs long
- Audio on a video render: an mp3 URL, with audio_duration set to auto to match the video length, or explicit trim timestamps at either end
A Placid account and an API token created under Settings > API, supplied as PLACID_API_TOKEN. Node.js 18 or newer; run it with npx @felores/placid-mcp-server. Assets are referenced by URL rather than uploaded, so the images, video and audio you pass have to be reachable over the web. Video renders consume Placid credits — every 10 seconds of video uses 10 credits.
One command plus a key — npx -y @smithery/cli install @felores/placid-mcp-server --client claude, then supply credentials