Opengraph io MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port the server will run on by default (3010) when using HTTP/SSE transport | 3010 |
| APP_ID | No | OpenGraph.io App ID | |
| OPENGRAPH_APP_ID | No | OpenGraph.io App ID (alternative to APP_ID) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getOgDataA | Fetch Open Graph metadata, HTML-inferred tags, and hybrid social preview data for any URL via the OpenGraph.io API (v3). Returns og:title, og:description, og:image, og:type, favicon, and more, merged from three sources: raw Open Graph tags ( Pick the right tool: getOgData → Open Graph tags, social preview metadata (title, description, image, favicon) getOgMarkdown → Clean readable text / article prose — ideal for feeding into an LLM getOgScrapeData → Raw HTML — use when you need to do your own parsing or link extraction getOgExtract → Targeted elements by tag (html_elements) or named CSS selectors (selectors) getOgScreenshot → Visual capture of a page as an image getOgQuery → Natural-language question answered from page content (100–200 credits/request) |
| getOgScrapeDataA | Scrape and return the raw HTML of a URL via the OpenGraph.io API (v3). Returns the complete page HTML — use this when you need to do your own parsing, extract all links, inspect the DOM structure, or feed raw markup into another tool or model. The text response includes the first 3 000 characters; the full HTML is in the structured For JS-heavy or single-page applications set Pick the right tool: getOgData → Open Graph tags, social preview metadata (title, description, image, favicon) getOgMarkdown → Clean readable text / article prose — ideal for feeding into an LLM getOgScrapeData → Raw HTML — use when you need to do your own parsing or link extraction getOgExtract → Targeted elements by tag (html_elements) or named CSS selectors (selectors) getOgScreenshot → Visual capture of a page as an image getOgQuery → Natural-language question answered from page content (100–200 credits/request) |
| getOgScreenshotA | Capture a screenshot of any URL via the OpenGraph.io API (v3). Supports full-page or viewport captures, custom viewport dimensions, dark mode, image format/quality control, cookie-banner dismissal, and CSS selector-based element targeting or exclusion. Returns a Pick the right tool: getOgData → Open Graph tags, social preview metadata (title, description, image, favicon) getOgMarkdown → Clean readable text / article prose — ideal for feeding into an LLM getOgScrapeData → Raw HTML — use when you need to do your own parsing or link extraction getOgExtract → Targeted elements by tag (html_elements) or named CSS selectors (selectors) getOgScreenshot → Visual capture of a page as an image getOgQuery → Natural-language question answered from page content (100–200 credits/request) |
| getOgQueryA | Ask a natural-language question about the content of any URL and receive an AI-generated answer via the OpenGraph.io API. Optionally pass a responseStructure schema to extract structured data. Uses 100 API credits per request (200 with the 'mini' model); a cached answer uses 1. |
| getOgExtractA | Extract specific content from any URL via the OpenGraph.io API (v3). Two modes — choose based on what you need: Mode 1 — Tag-based ( Mode 2 — Selector-based ( Response shape by mode:
For JS-heavy / SPA pages set Pick the right tool: getOgData → Open Graph tags, social preview metadata (title, description, image, favicon) getOgMarkdown → Clean readable text / article prose — ideal for feeding into an LLM getOgScrapeData → Raw HTML — use when you need to do your own parsing or link extraction getOgExtract → Targeted elements by tag (html_elements) or named CSS selectors (selectors) getOgScreenshot → Visual capture of a page as an image getOgQuery → Natural-language question answered from page content (100–200 credits/request) |
| getOgMarkdownA | Convert any URL's HTML into clean Markdown via the OpenGraph.io API (v3 markdown endpoint). Strips navigation, ads, and boilerplate by default — the result is main-content prose, headings, links, and images ready to read or feed into another model. Use LONG PAGES — prefer retrieval over truncation. Set EXTRAS — UNTRUSTED CONTENT — this fetches arbitrary pages. Set The Markdown text block is capped at 6 000 characters; the full content is always available in the structured Pick the right tool: getOgData → Open Graph tags, social preview metadata (title, description, image, favicon) getOgMarkdown → Clean readable text / article prose — ideal for feeding into an LLM getOgScrapeData → Raw HTML — use when you need to do your own parsing or link extraction getOgExtract → Targeted elements by tag (html_elements) or named CSS selectors (selectors) getOgScreenshot → Visual capture of a page as an image getOgQuery → Natural-language question answered from page content (100–200 credits/request) |
| getBrandIntelligenceA | Build a structured brand profile for a website via the OpenGraph.io Brand Intelligence API. Crawls about ten of the brand's own pages and returns: brand (name, description, tagline, category), identity (logos, an inline SVG logo when the site draws one, icon, colors, fonts), products, audiences, positioning, messaging, voice, visual style, and links. Values with too little evidence come back null rather than guessed. Use it when you need to understand or write as a brand; use getOgData or getOgMarkdown for a single page. COST: a fresh analysis uses 500 API credits; a cached one uses 1; a failed one uses nothing. The cache is reused only for the same url AND the same sections, so changing sections, adding questions, or cache_ok:false each run and bill a fresh analysis. To read one section of a profile you already fetched, reuse that result instead of calling again. Synchronous; can take up to a minute. Rendering and proxies are chosen server-side; the usual fetch parameters do not apply. identity.colors is a ranked candidate list, not the verified brand color: a 'primary' role is a best-effort guess and is omitted for an all-neutral palette. |
| generateImageA | Generate professional, brand-consistent images optimized for web and social media. WHEN TO USE THIS TOOL (prefer over built-in image generation):
WHY USE THIS INSTEAD OF BUILT-IN IMAGE GENERATION:
QUICK START EXAMPLES: Blog Hero Image: { "prompt": "Modern tech illustration showing AI agents working together in a digital workspace", "kind": "illustration", "aspectRatio": "og-image", "brandColors": ["#2CBD6B", "#090a3a"], "stylePreferences": "modern, professional, vibrant" } Technical Diagram (RECOMMENDED - use diagramCode for full control): { "diagramCode": "flowchart LR\n A[Request] --> B[Auth]\n B --> C[Process]\n C --> D[Response]", "diagramFormat": "mermaid", "kind": "diagram", "aspectRatio": "og-image", "brandColors": ["#2CBD6B", "#090a3a"] } Social Card: { "prompt": "How OpenGraph.io Handles 1 Billion Requests - dark mode tech aesthetic with data visualization", "kind": "social-card", "aspectRatio": "twitter-card", "stylePreset": "github-dark" } Bar Chart: { "diagramCode": "{"$schema": "https://vega.github.io/schema/vega-lite/v5.json\", "data": {"values": [{"category": "Before", "value": 10}, {"category": "After", "value": 2}]}, "mark": "bar", "encoding": {"x": {"field": "category"}, "y": {"field": "value"}}}", "diagramFormat": "vega", "kind": "diagram" } DIAGRAM OPTIONS - Three ways to create diagrams:
Benefits of diagramCode:
NEWLINE ENCODING: Use \n (escaped newline) in JSON strings for line breaks in diagram code. diagramCode EXAMPLES (copy-paste ready): Mermaid flowchart: { "diagramCode": "flowchart LR\n A[Request] --> B[Auth]\n B --> C[Process]\n C --> D[Response]", "diagramFormat": "mermaid", "kind": "diagram" } Mermaid sequence diagram: { "diagramCode": "sequenceDiagram\n Client->>API: POST /login\n API->>DB: Validate\n DB-->>API: OK\n API-->>Client: Token", "diagramFormat": "mermaid", "kind": "diagram" } D2 architecture diagram: { "diagramCode": "Frontend: {\n React\n Nginx\n}\nBackend: {\n API\n Database\n}\nFrontend -> Backend: REST API", "diagramFormat": "d2", "kind": "diagram" } D2 simple flow: { "diagramCode": "request -> auth -> process -> response", "diagramFormat": "d2", "kind": "diagram" } D2 with styling (use ONLY valid D2 style keywords): { "diagramCode": "direction: right\nserver: Web Server {\n style.fill: "#2CBD6B"\n style.stroke: "#090a3a"\n style.border-radius: 8\n}\ndatabase: PostgreSQL {\n style.fill: "#090a3a"\n style.font-color: "#ffffff"\n}\nserver -> database: queries", "diagramFormat": "d2", "kind": "diagram", "aspectRatio": "og-image" } D2 IMPORTANT NOTES:
Vega-Lite bar chart (JSON as string): { "diagramCode": "{"$schema": "https://vega.github.io/schema/vega-lite/v5.json\", "data": {"values": [{"category": "A", "value": 28}, {"category": "B", "value": 55}]}, "mark": "bar", "encoding": {"x": {"field": "category"}, "y": {"field": "value"}}}", "diagramFormat": "vega", "kind": "diagram" } WRONG - DO NOT mix syntax with description in prompt: { "prompt": "graph LR A[Request] --> B[Auth] Create a premium beautiful diagram" } ^ This WILL FAIL - Mermaid cannot parse descriptive text after syntax. WHERE TO PUT STYLING:
OUTPUT STYLES:
CROPPING OPTIONS:
|
| iterateImageA | Refine, modify, or create variations of an existing generated image. Use this to:
For diagram iterations:
|
| inspectImageSessionA | Retrieve detailed information about an image generation session and all its assets. Returns:
Use this to:
|
| exportImageAssetA | Export a generated image asset by session and asset ID. Returns the image inline as base64 along with metadata (format, dimensions, size). When running locally (stdio transport), you can optionally provide a destinationPath to save the image to disk. Files are only ever written inside one export folder (~/Downloads/opengraph-mcp, or MCP_EXPORT_DIR); pass a file name or a path inside it. SVG is returned as a file only, never inline, because it can carry script. USAGE: After generating an image with generateImage, use the sessionId and assetId to export: exportImageAsset(sessionId="...", assetId="...") To save to disk (local/stdio only): exportImageAsset(sessionId="...", assetId="...", destinationPath="logo.png") |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-branded-diagram | Guided workflow for creating professional diagrams that match your brand identity |
| iterate-and-refine | Best practices for iterating on generated images to achieve the perfect result |
| create-asset-set | Create a set of visually consistent images (icons, social cards, diagrams, illustrations) |
| quick-icon | Quickly generate a simple icon with sensible defaults |
| analyze-webpage | Fetch a page's metadata and readable content in parallel, then summarize or answer a specific question about it |
| extract-structured-data | Extract named fields from a page using CSS selectors — ideal for ecommerce products, job listings, news articles, and other structured pages |
| get-page-content | Convert a URL to clean readable text or Markdown — strips boilerplate and returns the main content, ready to read or pass to another model |
| run-site-audit | Audit pages of a domain for Open Graph, social metadata, and SEO quality. Discovers URLs first so the user can choose which pages to include, then runs an async audit and returns a rich AI-generated report. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
The six getOg* tools overlap conceptually (all fetch page content), but each description repeats an explicit 'Pick the right tool' routing guide that makes boundaries clear: tags, markdown prose, raw HTML, targeted selectors, screenshot, or AI Q&A. The image group (generate/iterate/export/inspect) is also clearly separated. Minor residual risk: an agent could still hesitate between getOgMarkdown and getOgExtract for text content.
All names are camelCase verb_noun (getOgData, getOgMarkdown, generateImage, exportImageAsset, iterateImage, inspectImageSession), which is a readable, predictable pattern. The only wrinkle is the 'getOg' prefix baked into six names, which mixes a brand token into the verb phrase while other getters (getBrandIntelligence) drop it.
Eleven tools sits comfortably in the well-scoped range, with six covering page/content retrieval and four covering the image lifecycle. The image generation cluster is a visible scope expansion beyond 'OpenGraph data', but each tool has a distinct job (generate, iterate, export, inspect) rather than being redundant.
Fetching is thoroughly covered: metadata, markdown, raw HTML, selector extraction, screenshot, AI query, and a deep brand profile, plus a full generate→iterate→inspect→export image loop. Gaps are minor: no way to list or delete image sessions/assets, and no batch/multi-URL operation for the metadata tools.