A
licenseA
qualityC
maintenanceGenerates 1200x630 social preview images (PNG/SVG) from a title and tag line via the oganvil OG image API, returning hosted render URLs and quota usage directly from MCP-capable clients.
2
MIT
OgForge
Server Details
Render 1200x630 Open Graph social preview images from templates; returns a cacheable PNG URL.
Ownership verified
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A4.2/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusing it with another. Its purpose (rendering an OG/social-card image from a template) is stated unambiguously in the description.
Naming Consistency5/5
The single tool uses a clear verb_noun snake_case pattern (create_og_image). Nothing else exists to clash with it, so consistency is trivially satisfied.
Tool Count3/5
A single tool is borderline thin even for a narrowly scoped render service. Useful adjacent operations (e.g. listing available templates or previewing) are absent, leaving the surface minimal.
Completeness4/5
The core domain — producing an OG image and its meta tags — is fully covered by the one operation, and templates are enumerated in the description. Minor gaps exist (no programmatic template listing or batch/multi-image generation), but nothing blocks the primary workflow.
Available Tools
1 toolcreate_og_imageCreate an Open Graph social preview imageARead-onlyIdempotentInspect
Render a 1200x630 PNG Open Graph / social-card image from a template and return its public URL (for og:image and twitter:image tags), size and ready-to-paste meta tags. Templates: blog, launch, docs, minimal, gradient. Optional inline PNG with include_image. Same engine, cache and free-tier limits as GET /api/og. Read-only (renders are cached; nothing is stored about you).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bg | No | Background hex color, e.g. 0f172a. | |
| fg | No | Text hex color. | |
| logo | No | Public https:// URL of a PNG, JPEG or SVG logo (max 512 characters, 300 KB). Fetched by OgForge's server. | |
| site | No | Site or brand name, e.g. "example.dev". Max 60 characters (longer text is truncated with "…"). | |
| emoji | No | One emoji, e.g. 🚀 | |
| label | No | Small pill or tag, e.g. "Engineering". Max 40 characters (longer text is truncated with "…"). | |
| theme | No | Color scheme (default depends on the template). | |
| title | Yes | Headline, e.g. "How we cut API latency by 60%". Max 120 characters (longer text is truncated with "…"). | |
| accent | No | Accent hex color. | |
| author | No | Author or byline. Max 60 characters (longer text is truncated with "…"). | |
| subtitle | No | Secondary line / description. Max 200 characters (longer text is truncated with "…"). | |
| template | No | Layout (default blog). | |
| include_image | No | Also return the PNG inline as MCP image content (default false; usually 30-150 KB). |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| etag | No | |
| tier | Yes | |
| bytes | No | |
| cache | Yes | MISS, HIT-MEMORY or HIT-EDGE |
| width | Yes | |
| height | Yes | |
| warning | No | e.g. logo_fetch_failed: the image rendered without the logo. |
| template | Yes | |
| image_url | Yes | Public PNG URL (GET /api/og?...). Use it as og:image / twitter:image. |
| meta_tags | No | Ready-to-paste og:image / twitter:card meta tags. |
| truncated | No | Fields that were shortened to fit. |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is largely covered. The description adds real value on top: renders are cached, nothing is stored about the requester, and free-tier/rate limits are mentioned, which an agent needs for retry and quota planning.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the output artifact and dimensions, then supporting details in compact clauses. Slightly dense with multiple parenthetical asides, but every sentence carries information relevant to calling the tool correctly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 13 parameters, an output schema present, and rich annotations, the definition is complete: it covers output format, caching, limits, and the template set without needing to explain return values, which the output schema handles.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, including enum values for template and theme and truncation limits for text fields, so the schema does the heavy lifting. The description only restates the template list and include_image, adding nothing beyond the structured fields – the baseline 3 is correct.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb and resource: renders a 1200x630 PNG Open Graph/social-card image from a template and returns its public URL, size and meta tags. It also names the five templates and the include_image option, so the agent knows exactly what the tool produces without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
States the intended use case (og:image and twitter:image tags) and ties its behavior to the sibling HTTP endpoint GET /api/og, noting shared engine, cache and free-tier limits. There is no explicit when-not or alternative tool to route to (none exists), but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
create_og_image
Related MCP Connectors
Deterministic image rendering for agents: JSON template in, on-brand PNG out.
Generate branded images at scale: design templates and render them to PNGs by prompt.
Social cards and OG images from designed templates: card from a URL, presets, meta tags, link checks
Generates 1200x630 OG social preview images (PNG/SVG). Tools: generate_og_image, get_quota.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenancePaste a URL to see exactly how it renders as a social card on Twitter, LinkedIn, Facebook, and Slack. Generate custom OG images from templates.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to render 1200×630 Open Graph social card images from a title, subtitle, and theme, returning a public PNG URL. It also provides pricing information for purchasing one-time forever credits.MIT
- AlicenseNot gradedqualityBmaintenanceGenerates social cards and Open Graph images from designed templates for any web page, with previews across platforms, meta tag generation, and optional account features for custom templates and hosted image URLs.MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.