Full canvas control
Create, update, duplicate, and delete canvases; list and apply templates; render and manage finished images — all through typed MCP tools.
ogdynamic ships an MCP server that exposes the whole canvas workflow. Create a design from a prompt, edit layers conversationally, and render finished images — inside Claude, Cursor, VS Code, or any MCP client.
MCP client
canvas server · OAuth 2.1
create_canvas → apply template "launch-bold"
update_canvas → headline "Ship faster"
create_render → png
ten tools · canvases, renders, templates
Create, update, duplicate, and delete canvases; list and apply templates; render and manage finished images — all through typed MCP tools.
Ask your assistant for a 1200×630 launch banner, refine the headline and colors through follow-up messages, and render without opening a browser.
MCP clients register through OAuth 2.1 dynamic client registration and authorize with PKCE — the same account permissions as the web app apply.
Setup stays close to the tool you already use, while ogdynamic handles template rendering and delivery.
Point your MCP client at your ogdynamic MCP URL. The client discovers the server and starts OAuth 2.1 registration automatically.
Sign in and approve the client. Access is scoped to your own canvases, renders, and templates.
Ask for a canvas, iterate on layers and text, apply a template, and render the final image — the assistant calls the tools for you.
The canvas server lives at its own endpoint under /mcp, so future ogdynamic MCP servers (video and more) can sit alongside it. On first connect, the client registers itself through OAuth 2.1 dynamic registration, opens your browser for the ogdynamic consent screen, and stores its token — no manual API keys.
Optional but recommended: teach your agent the canvas workflow — document format, fonts, styles, overrides. Requires Node.js 22.20+.
Run once from your terminal; the CLI opens the browser for authorization.
claude mcp add --transport http ogdynamic-canvas https://ogdynamic.com/mcp/canvas
Run once from your terminal (append --global for all projects); the OAuth browser flow starts automatically on first use.
opencode mcp add --url https://ogdynamic.com/mcp/canvas ogdynamic-canvas
Add to ~/.codex/config.toml, then start a session.
[mcp_servers.ogdynamic-canvas] url = "https://ogdynamic.com/mcp/canvas"
Add to ~/.zcode/cli/config.json (user) or <repo>/.zcode/config.json (workspace); the server connects automatically on the next session.
{
"mcp": {
"servers": {
"ogdynamic-canvas": {
"type": "http",
"url": "https://ogdynamic.com/mcp/canvas"
}
}
}
}Save as .cursor/mcp.json in your project (or Settings → MCP → Add server).
{
"mcpServers": {
"ogdynamic-canvas": {
"url": "https://ogdynamic.com/mcp/canvas"
}
}
}Save as .vscode/mcp.json in your workspace.
{
"servers": {
"ogdynamic-canvas": {
"type": "http",
"url": "https://ogdynamic.com/mcp/canvas"
}
}
}Desktop apps without native HTTP transport can connect through mcp-remote.
{
"mcpServers": {
"ogdynamic-canvas": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ogdynamic.com/mcp/canvas"]
}
}
}Point any client implementing streamable HTTP at the endpoint above.
MCP server URL: https://ogdynamic.com/mcp/canvas Transport: streamable HTTP + OAuth 2.1 (PKCE)
Values that flow between MCP and your ogdynamic templates.
The MCP server exposes your canvas workflow as typed tools. Your assistant composes them: create a canvas, apply a template, override the headline, render a PNG.
Every action respects your account permissions, and renders use the same deterministic engine and caching as the web editor and public image URLs.
Practical details for teams connecting ogdynamic to MCP.
The Model Context Protocol is an open standard that lets AI assistants call external tools. ogdynamic runs an MCP server, so assistants like Claude — and editors like Cursor and VS Code — can design and render images on your behalf.
Any client that implements MCP and supports OAuth 2.1 authorization: Claude, Cursor, VS Code extensions, and custom MCP clients.
Yes. Tools cover creating, updating, duplicating, and deleting canvases, so an assistant can iterate on an existing design as well as start new ones.
No. MCP uses the same rendering engine, override system, and caching as the web editor and the public image URLs — output is pixel-identical.
Design your template once — the MCP integration keeps every generated image current.
Start generating free