Let an AI agent make and maintain designs with the Ridvay MCP server
Updated 2026-09-04
The Model Context Protocol (MCP) is how AI assistants call tools. Ridvay ships an MCP server, so an assistant can compose a poster itself, ask Ridvay’s AI to design one, refine it, export PNG, PDF-quality images and video, share it, and — new — keep a living design up to date by changing its variables. Every design lands in your account like any other.
There are two ways to connect. The hosted endpoint at mcp.ridvay.com needs no install: add https://mcp.ridvay.com/mcp as a connector and sign in with your Ridvay account when the client asks (OAuth), or paste a URL or header that carries an API key. The open-source package runs the same server locally via npx if you prefer to keep the key on your machine.
How to do it
Connect by signing in (claude.ai, ChatGPT, Claude Code, Cursor)
Add https://mcp.ridvay.com/mcp as a connector with no key. The client discovers Ridvay’s sign-in, sends you to ridvay.com to approve “Connect Claude to Ridvay?” (or ChatGPT, or the client’s name), and comes back connected. Behind the scenes it holds an API key named “Claude (OAuth)” in your account; delete that key on the API keys page to disconnect.
Or create an API key
For clients without sign-in support: at ridvay.com open your account and go to API keys. Create a key and copy it once; it is shown only at creation. The key is what the agent uses, and revoking it disconnects the agent.
Connect by URL (claude.ai, ChatGPT)
If you would rather not sign in: in claude.ai open Settings → Connectors → Add custom connector and paste https://mcp.ridvay.com/mcp/<your-key> as the URL; no extra authentication step. In ChatGPT use Settings → Connectors (developer mode) with the same URL. Treat that URL like a password.
Connect by header (Claude Code, Cursor, desktop clients)
Point the client at https://mcp.ridvay.com/mcp and send your key as a Bearer token. Claude Code: claude mcp add --transport http ridvay https://mcp.ridvay.com/mcp --header "Authorization: Bearer sk-ridvay-…". Local alternative: claude mcp add ridvay --env RIDVAY_API_KEY=sk-ridvay-… -- npx -y ridvay-mcp.
Ask for a design
“Make a story-size poster for our weekend sale” — the assistant reads the design guide, composes the design with create_poster (no credits), or falls back to generate_poster (Ridvay’s AI, uses credits). Links to view, edit and a live image come back in chat. Add “use my Bakery brand” and it calls list_brands and passes the brand id.
Refine, export, share
refine_poster applies changes in plain words; export_poster returns a PNG or JPEG at up to 4× size; animate_poster plus export_video makes an MP4; share_design returns the public page, an editable copy, the live-image PNG and the full-screen screen link for a TV.
Keep a living design updated
Create a design whose text uses variables such as {{price}} (declare them in the design’s vars, or in the Living design panel in Studio). Then the agent — or a script, or Zapier — calls set_values with new values whenever they change. The shared page, the live image and the screen view refresh within a minute. get_values shows what is declared and current.
Tips
- Ask the assistant to compose the design itself first; it is faster and free. Ridvay’s own AI is the fallback for briefs the assistant cannot lay out.
- One key per agent or workflow, named for it, so revoking one does not disconnect the others.
- For a menu board on a screen: create once, share_design, open the screen link on the TV, then set_values every morning.
- list_designs finds IDs by title, so the agent can pick up a design you made in the editor.
Frequently asked questions
- Which assistants work?
- Any MCP client: Claude (claude.ai connectors, Claude Code, Claude Desktop), ChatGPT connectors, Cursor, GitHub Copilot in VS Code, Windsurf and others. Hosted needs a URL or a header; local needs Node and npx.
- Does it use my credits?
- Only when the assistant asks Ridvay’s AI to generate, refine or recreate. Composing a design itself, exporting, sharing and updating values are free.
- Is the URL with my key safe?
- It is a convenience for clients that cannot send headers; anyone with the URL can act as you, so keep it private and prefer the header form where the client supports it. Revoke the key on the API keys page at any time.
- Where do the designs go?
- Into the account that owns the key, under My designs, editable in Studio like any other. A shared design gets a public page, a live image URL and a screen link; private designs stay private.
Try it on your own design
Free to start, nothing to install.
Related guides
- Living designsLiving designs: a menu board or price board that updates itself on any screen
- Generate from a promptGenerate a complete, editable design from a prompt
- Export and shareExport PNG, SVG, PDF, PowerPoint, GIF and video, or share an editable link
- Brand kitSet up a brand kit so every design starts on brand