Ogmake MCP

What ogmake/ogmake-mcp MCP server does

ogmake/ogmake-mcp MCP server gives an MCP client access to ogmake.com image-generation features. It can discover registered templates, render social cards, produce image URLs, create framework-specific metadata snippets, and report account usage. The server also supports rendering raw HTML and CSS into stored PNG, JPG, WebP, or PDF files when an API key is available.

The available rendering paths depend on configuration. Authenticated rendering accepts a template and optional parameters such as format, preset, scale, version, background, and Google Fonts family. Without an API key, the image-rendering tool can still create a watermarked image from a title, optional description, and site name, but it returns image bytes only rather than a hosted URL.

How it works

The package is a local stdio MCP process started with npx -y ogmake-mcp. An MCP client sends tool calls to the process, which then communicates with ogmake.com where the selected operation requires the service API. list_templates does not require credentials and returns template IDs, versions, and parameter schemas.

For larger jobs, create_batch starts an asynchronous batch containing up to 500 renders and immediately returns a batch ID. get_batch retrieves the batch state and the stored URL or error for each item. A batch may also provide an HTTPS webhook URL for a signed batch.completed event.

build_image_url has two local configuration modes. With a signing secret and matching signing key ID, it creates an HMAC-SHA256-signed URL locally. With a public key ID instead, it creates an unsigned /p/:keyId/:template URL; the key must be public and configured to allow the requested template on ogmake.com.

Setup and configuration

Start the server with npx -y ogmake-mcp, then register that command in an MCP client. Claude Code can add it with claude mcp add; Cursor can use the same stdio configuration block in its MCP settings. Set OGMAKE_API_KEY for authenticated rendering, HTML rendering, batches, and usage reporting. The API origin can be changed with the optional OGMAKE_BASE_URL variable.

For local URL signing, provide OGMAKE_SIGNING_SECRET and OGMAKE_SIGNING_KEY_ID together. For unsigned public URLs, provide OGMAKE_PUBLIC_KEY_ID. The API key and signing secret are read once at startup and are not returned in tool results, errors, or logs.

Tools and capabilities

ogmake/ogmake-mcp MCP server exposes these operations:

• list_templates discovers templates and their parameter schemas.
• render_image creates authenticated or watermarked social-card images.
• render_html converts raw HTML and CSS into a stored file.
• create_batch and get_batch manage asynchronous render batches.
• build_image_url constructs signed or public image URLs without rendering.
• og_snippet creates og:image and twitter:image metadata for HTML, Hugo, Jekyll, Rails, Laravel, Django, WordPress, or Ghost.
• get_usage reports the current billing period’s render usage and quota.

Limitations and notes

Authenticated tools require OGMAKE_API_KEY; the free rendering path is watermarked and does not store an image URL. URL signing requires both signing variables, while public URL generation depends on an appropriately configured public key. The server itself is local, but operations that render or retrieve account data depend on the ogmake.com API unless the operation is local template discovery or URL signing.

The package is licensed under MIT. Its documented installation examples cover Claude Code and Cursor, and the process communicates through standard MCP stdio.