mcpField
O
ogmake

ogmake

Local
ogmake.comMedia & Design0Updated 3w ago

About ogmake

ogmake is a local stdio MCP server for generating og:image cards through ogmake.com. It offers template-based rendering, HTML/CSS rendering, batch jobs, URL signing, and metadata snippets, with some functions available without an API key.

Key features

  1. 01List image templates and schemas
  2. 02Render images from templates or HTML/CSS
  3. 03Create and check render batches
  4. 04Build and locally sign image URLs
  5. 05Generate framework-specific metadata snippets
  6. 06Check account usage and quota

Use cases

  1. 01Create social preview images for a site
  2. 02Render batches of image cards
  3. 03Generate signed image URLs without sending the signing secret
  4. 04Add Open Graph and Twitter image tags

MCP support

Exposes ogmake.com image-generation and URL-building operations as MCP tools over local stdio. Authenticated rendering and batch operations use an API key; URL signing can be performed locally.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-ogmake": {
"command": "npx",
"args": [
"-y",
"ogmake-mcp"
],
"env": {
"OGMAKE_API_KEY": "<OGMAKE_API_KEY>"
}
}
}
}
Run commandnpx -y ogmake-mcp
Environment variables to set
OGMAKE_API_KEYSecretogmake.com API key. Optional: without it render_image uses the free watermarked endpoint.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmogmake-mcp0.1.2

Tools

8

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project 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
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:

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

pnpm --filter ogmake-mcp run test        # unit tests, 100% coverage
pnpm --filter ogmake-mcp run test:e2e    # spawns the packed CLI over stdio against a local wrangler dev
pnpm --filter ogmake-mcp run build       # tsup bundle -> dist/index.js
pnpm --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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.