ogdynamic

What the MCP integration covers.

Full canvas control

Create, update, duplicate, and delete canvases; list and apply templates; render and manage finished images — all through typed MCP tools.

Conversational design

Ask your assistant for a 1200×630 launch banner, refine the headline and colors through follow-up messages, and render without opening a browser.

Secure by default

MCP clients register through OAuth 2.1 dynamic client registration and authorize with PKCE — the same account permissions as the web app apply.

From connection to generated images.

Setup stays close to the tool you already use, while ogdynamic handles template rendering and delivery.

01

Add the MCP server

Point your MCP client at your ogdynamic MCP URL. The client discovers the server and starts OAuth 2.1 registration automatically.

02

Authorize your account

Sign in and approve the client. Access is scoped to your own canvases, renders, and templates.

03

Design through conversation

Ask for a canvas, iterate on layers and text, apply a template, and render the final image — the assistant calls the tools for you.

Add the MCP server to your client.

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+.

Claude Code

Run once from your terminal; the CLI opens the browser for authorization.

claude mcp add --transport http ogdynamic-canvas https://ogdynamic.com/mcp/canvas

OpenCode

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

Codex

Add to ~/.codex/config.toml, then start a session.

[mcp_servers.ogdynamic-canvas]
url = "https://ogdynamic.com/mcp/canvas"

ZCode

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"
      }
    }
  }
}

Cursor

Save as .cursor/mcp.json in your project (or Settings → MCP → Add server).

{
  "mcpServers": {
    "ogdynamic-canvas": {
      "url": "https://ogdynamic.com/mcp/canvas"
    }
  }
}

VS Code

Save as .vscode/mcp.json in your workspace.

{
  "servers": {
    "ogdynamic-canvas": {
      "type": "http",
      "url": "https://ogdynamic.com/mcp/canvas"
    }
  }
}

Claude Desktop

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"]
    }
  }
}

Any MCP client

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)

Built for real MCP workflows.

Canvas tools

  • Create, update, and duplicate canvases
  • Get a canvas document or list your canvases
  • Delete canvases you no longer need
  • Start from the template library

Render tools

  • Create renders with URL overrides
  • List previous renders per canvas
  • Delete outdated renders
  • webp, png, and jpeg output

Client ecosystem

  • Works with Claude and other MCP-native assistants
  • Cursor and VS Code supported
  • Any client implementing MCP can connect

MCP fields

Values that flow between MCP and your ogdynamic templates.

create_canvasupdate_canvasduplicate_canvasdelete_canvaslist_canvasesget_canvascreate_renderlist_rendersdelete_renderlist_templates

A conversation that renders

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.

MCP integration questions.

Practical details for teams connecting ogdynamic to MCP.

What is 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.

Which clients can connect?

Any client that implements MCP and supports OAuth 2.1 authorization: Claude, Cursor, VS Code extensions, and custom MCP clients.

Can the assistant edit existing canvases?

Yes. Tools cover creating, updating, duplicating, and deleting canvases, so an assistant can iterate on an existing design as well as start new ones.

Are MCP renders different from web renders?

No. MCP uses the same rendering engine, override system, and caching as the web editor and the public image URLs — output is pixel-identical.