Mcp

com.ogmakev0.1.2Updated Oct 10, 2026

Generate og:image social cards and signed ogmake.com image URLs from your AI assistant.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Generates og:image social cards and signed ogmake.com image URLs from an AI assistant.

What it does
A local stdio server for ogmake.com og:image generation. Tools include list_templates (template ids, versions and params schemas), render_image (template-based social cards, or a watermarked free image from a title), render_html (raw HTML/CSS to PNG/JPG/WebP/PDF), create_batch and get_batch for async batches of up to 500 renders, build_image_url for signed or public image URLs, og_snippet for framework meta tags, and get_usage for the billing period's quota.
When to use it
Useful when an assistant should produce social share images or og:image meta tags for pages, or run larger render batches, without leaving the chat. Worth adding if you already use ogmake.com or want template-driven card generation; without an API key only listing, watermarked free renders, URL building and snippet generation work.
Requirements
Runs locally via npx -y ogmake-mcp (Node.js). Optional environment variables: OGMAKE_API_KEY for authenticated render_image, render_html, create_batch, get_batch and get_usage; OGMAKE_BASE_URL to override the API origin; OGMAKE_SIGNING_SECRET and OGMAKE_SIGNING_KEY_ID for local URL signing; OGMAKE_PUBLIC_KEY_ID for unsigned public URLs. Network access to ogmake.com is needed for rendering.
Before you install
Authenticated rendering spends credits (render_html costs 2 credits) and create_batch can start up to 500 renders, so usage costs money. Secrets OGMAKE_API_KEY and OGMAKE_SIGNING_SECRET are read from the environment; the README says they stay local and are not echoed. An optional webhookUrl receives a signed batch.completed event. Renders and batches are sent to ogmake.com, and hosted URLs are stored there.

Installation

In SourceWeft

  1. Open Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ogmake-mcp

Local stdio MCP server for ogmake.com og:image generation. Run it with npx -y ogmake-mcp.

Tools

  • list_templates — lists every registered og:image template id, version, and its params JSON Schema. No API key required.
  • render_html — renders raw HTML/CSS to a stored PNG/JPG/WebP/PDF (2 credits; needs OGMAKE_API_KEY).
  • render_image — renders an og:image.
    • With OGMAKE_API_KEY set: renders template (+ optional params, format, preset, scale, v, bg, font — a Google Fonts family) via the authenticated API and returns its hosted URL plus the image bytes.
    • With no OGMAKE_API_KEY: renders a watermarked free image from title (+ optional description, site) and returns image bytes only — no hosted URL (the free endpoint never stores one).
  • create_batch — starts an async batch of up to 500 renders (POST /v1/batch); returns a batch_id immediately. Optional webhookUrl (https) gets a signed batch.completed event. Needs OGMAKE_API_KEY.
  • get_batch — a batch's status plus each item's stored URL or error. Needs OGMAKE_API_KEY.
  • build_image_url — builds an image URL for template without rendering it.
    • With OGMAKE_SIGNING_SECRET + OGMAKE_SIGNING_KEY_ID set: signs the URL locally (HMAC-SHA256) — the signing secret never leaves your machine and is never sent to the model.
    • Else with OGMAKE_PUBLIC_KEY_ID set: builds an unsigned /p/:keyId/:template URL (the key must be marked public and allow-list that template on ogmake.com).
  • og_snippet — renders the og:image/twitter:image meta tag snippet for a given framework (html, hugo, jekyll, rails, laravel, django, wordpress, ghost) and image URL.
  • get_usage — current billing period's render usage/quota for the OGMAKE_API_KEY account. Requires OGMAKE_API_KEY.

Every secret (OGMAKE_API_KEY, OGMAKE_SIGNING_SECRET) stays local: it is read from the environment once at startup and is never echoed back in a tool result, error message, or log line.

Environment variables

VariableRequired for
OGMAKE_API_KEYauthenticated render_image, render_html, create_batch, get_batch, get_usage
OGMAKE_BASE_URLoptional — override the API origin (defaults to https://ogmake.com)
OGMAKE_SIGNING_SECRETlocal signing in build_image_url (base64url)
OGMAKE_SIGNING_KEY_IDlocal signing in build_image_url (paired with the secret above)
OGMAKE_PUBLIC_KEY_IDunsigned /p URLs in build_image_url

Install

Claude Code

sh
claude mcp add ogmake --env OGMAKE_API_KEY=og_live_... -- npx -y ogmake-mcp

Or add to .mcp.json (project scope) / ~/.claude.json (user scope); Cursor takes the same block in ~/.cursor/mcp.json:

json
{  "mcpServers": {    "ogmake": {      "command": "npx",      "args": ["-y", "ogmake-mcp"],      "env": { "OGMAKE_API_KEY": "og_live_..." }    }  }}

Without OGMAKE_API_KEY only list_templates, watermarked free render_image, build_image_url and og_snippet work.

Support: [email protected] · License: MIT

Development

sh
pnpm --filter ogmake-mcp run test        # unit tests, 100% coveragepnpm --filter ogmake-mcp run test:e2e    # spawns the packed CLI over stdio against a local wrangler devpnpm --filter ogmake-mcp run build       # tsup bundle -> dist/index.jspnpm --filter ogmake-mcp run pack        # build + npm pack -> pack-out/*.tgz

Development

vendor/ holds the SDK and request-signing helper this server bundles, so the repository builds standalone: npm install && npm run build && npm test.

Source: README.md at commit 5e1e287

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.2LatestOct 10, 2026