Skip to main content
Glama

OpenGraph MCP Server

opengraph-io-mcp is a Model Context Protocol (MCP) server that makes the OpenGraph.io API available to AI agents such as Claude, Cursor and LangGraph through the standard MCP interface.

Why? If you already use OpenGraph.io to unfurl links, scrape HTML, extract article text, or capture screenshots, you can now give the same capabilities to your autonomous agents without exposing raw API keys.

Global Installation

You can install this package globally via npm:

npm install -g opengraph-io-mcp

Related MCP server: screenshotfreeapi

Quick Install

The easiest way to configure OpenGraph MCP for any supported client:

# Interactive mode - guides you through setup
npx opengraph-io-mcp-install

# Direct mode - specify client and app ID
npx opengraph-io-mcp-install --client cursor --app-id YOUR_APP_ID

Supported clients: cursor, claude-desktop, windsurf, vscode, zed, jetbrains

Claude Desktop Extension

For Claude Desktop, download the .mcpb extension from the Releases page and open it. Claude Desktop asks for your App ID once and stores it securely.

Authentication

The hosted server at https://mcp.opengraph.io/mcp uses OAuth 2.1. You sign in once in your browser and choose which OpenGraph.io API key to authorize; nothing secret goes into a config file, and you can revoke access from the dashboard at any time. OAuth also unlocks the Open Graph Audit and Link Preview tools.

How it works: when a client connects without credentials, the server answers 401 with a WWW-Authenticate header pointing to

GET /.well-known/oauth-protected-resource
→ { "authorization_servers": ["https://dashboard-api.opengraph.io"] }

The client discovers the authorization server from there and opens https://dashboard.opengraph.io/oauth/consent in your browser. Clients with built in OAuth support need nothing but the URL. Clients that can only launch local commands connect through mcp-remote, a small bridge that runs on your machine and handles the same browser sign in.

The x-app-id header is deprecated on the hosted server. It still works for now, and responses to it carry a Deprecation header, but support is being removed. Move to one of the OAuth setups below. Running the server locally (the stdio transport, the CLI installer, or the Claude Desktop extension) uses your App ID directly and is not affected.


Client Configuration

Every setup below connects to the hosted server with OAuth. The first time a tool is used, your browser opens to sign in.

Add to Cursor Install in VS Code Install in VS Code Insiders

Claude Code

claude mcp add --transport http opengraph https://mcp.opengraph.io/mcp

Then run /mcp inside Claude Code and choose opengraph to sign in.

Claude Desktop

Settings → Connectors → Add custom connector, name it OpenGraph, and enter https://mcp.opengraph.io/mcp. Claude Desktop opens your browser to sign in.

If you prefer the config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows), use the mcp-remote bridge:

{
  "mcpServers": {
    "opengraph": {
      "command": "npx",
      "args": ["-y", "mcp-remote@0.14.3", "https://mcp.opengraph.io/mcp"]
    }
  }
}

Cursor

Install the OpenGraph.io plugin from the Cursor Marketplace, or add the server yourself.

Config location: ~/.cursor/mcp.json

{
  "mcpServers": {
    "opengraph": {
      "url": "https://mcp.opengraph.io/mcp"
    }
  }
}

VS Code

Config location: .vscode/mcp.json (in your project directory)

{
  "servers": {
    "opengraph": {
      "type": "http",
      "url": "https://mcp.opengraph.io/mcp"
    }
  }
}

Windsurf, JetBrains AI Assistant, Zed and other clients

If your client supports OAuth for remote servers, point it at https://mcp.opengraph.io/mcp with no headers. Otherwise connect through mcp-remote:

Windsurf (~/.codeium/windsurf/mcp_config.json) and JetBrains AI Assistant:

{
  "mcpServers": {
    "opengraph": {
      "command": "npx",
      "args": ["-y", "mcp-remote@0.14.3", "https://mcp.opengraph.io/mcp"]
    }
  }
}

Zed (~/.config/zed/settings.json, which uses context_servers):

{
  "context_servers": {
    "opengraph": {
      "command": "npx",
      "args": ["-y", "mcp-remote@0.14.3", "https://mcp.opengraph.io/mcp"]
    }
  }
}

mcp-remote stores its sign in under ~/.mcp-auth. Delete that folder to sign out.

Legacy x-app-id header (deprecated)

Only for setups that cannot use OAuth yet, while the hosted server still accepts it. Send your OpenGraph.io App ID as a header; Open Graph Audit and Link Preview tools are not available this way.

{
  "mcpServers": {
    "opengraph": {
      "url": "https://mcp.opengraph.io/mcp",
      "headers": { "x-app-id": "YOUR_OPENGRAPH_APP_ID" }
    }
  }
}

Available Tools

Two authentication tiers: Data and Image Generation tools work with OAuth, and also with a plain App ID when you run the server locally (the stdio transport or the Claude Desktop extension). Open Graph Audit and Link Preview tools require OAuth on the hosted server, since they bill against your organization's plan rather than a single API key.

OpenGraph.io Data Tools

All scraping/metadata tools default to the v3 API which enables auto_render, auto_proxy, and retry by default for higher success rates on complex pages. The query, extract and brand intelligence tools use v1.1 (see notes).

Tool Name

API Endpoint

Description

Documentation

Get OG Data

/api/3.0/site/<URL>

Fetch Open Graph metadata, HTML-inferred tags, and hybrid social preview data. Supports use_ai, ai_sanitize, load-more, proxy/retry, and all v3 smart defaults.

Docs

Get OG Scrape Data

/api/3.0/scrape/<URL>

Scrape raw HTML with full v3 rendering options including scroll-to-bottom, load-more clicks, and AI sanitization.

Docs

Get OG Screenshot

/api/3.0/screenshot/<URL>

Capture a screenshot. Supports full_page, dark_mode, capture_delay, navigationTimeout, hideSelectors, and custom viewport dimensions.

Docs

Get OG Query

/api/1.1/query/<URL>

Ask a natural-language question about a page's content. Uses v1.1 (100–200 credits/request) until billing path is updated for v3.

Docs

Get OG Extract

/api/1.1/extract/<URL>

Extract specific HTML elements (h1, p, a, img, etc.) by tag name. Stays on v1.1 — no v3 GET route exists for this endpoint.

Docs

Get OG Markdown

/api/3.0/markdown/<URL>

Convert any URL's HTML to clean Markdown. Strips nav/ads by default (only_main_content: true) and supports include_tags/exclude_tags selectors. For long pages, pass query with chunking to get back only the relevant passages, ranked, rather than the whole document. include_links/include_images/include_headings return structured link, image, and outline data. Returns page metadata, character and token usage, and — with ai_sanitize — a prompt-injection safety report.

Docs

Get Brand Intelligence

/api/1.1/brand/<URL>

Build a structured brand profile from about ten of a site's own pages: brand, identity (logos, icon, colors, fonts), products, audiences, positioning, messaging, voice, visual style, and links. Turn sections off with sections, ask up to 3 typed custom questions, and add per-field provenance with include_meta. Stays on v1.1, because v3's retry defaults would exceed its time budget. 500 credits per fresh analysis, 1 when cached.

Docs

Language detection: All tools send accept_lang: auto by default, which mirrors the request's Accept-Language header. Pass an explicit BCP 47 tag (e.g. en-US, fr) to override.

Requires OAuth 2.1 (see Authentication) and a plan that includes Open Graph Audit. These tools are available on the hosted server only. They are not listed when you run the server locally (the CLI installer or the Claude Desktop extension) or connect with the x-app-id header, since they need your organization identity, not just an API key.

Tool Name

Description

Discover Site URLs

Crawl a domain (sitemap + link discovery) and return every page found, grouped by depth, along with your remaining monthly audit quota.

Start Open Graph Audit

Kick off an async, multi-page SEO/social audit. Pass an explicit urls[] list (from discovery, a sitemap, or a codebase route scan) or let the backend crawl the domain itself. Returns an auditId immediately.

Get Open Graph Audit Status

Poll an in-progress audit (QUEUED → CRAWLING → SCORING → COMPLETE).

Get Open Graph Audit Report

Retrieve the full report once complete: overall score (0–100), an AI-generated executive summary, prioritized fixes, per-page scores, and Open Graph coverage rates.

Preview Page Audit

Instant, synchronous single-URL quality check with score + issues. Does not consume audit quota.

Get Link Preview

Instant, synchronous check of how a URL will render when shared — returns Facebook, Twitter/X, LinkedIn, and Google preview cards plus a quality score and fix list. Does not consume audit quota.

Delete Open Graph Audit

Permanently delete an audit and all of its results. Cannot be undone.

Monitoring & History Tools

Recurring audits, trend tracking, and change reporting. OAuth required; setMonitoringSchedule additionally requires the Open Graph Audit scheduling entitlement.

Tool Name

Description

List Websites

Every site the organization has audited, with current score and trend against the previous run, critical issue and regression counts, known page count, and next scheduled run. Pass a websiteId for one in detail.

List Open Graph Audits

Past audits, newest first, filterable by domain, status, date range, or website.

Get Open Graph Audit Changes

What changed since the previous run — new, fixed, and regressed issues, pages added or removed, and the score delta — plus prioritized issue groups. A regressed issue is one previously verified as fixed that has come back; this is tracked across runs by durable issue identity, not by diffing two lists.

Get Monitoring Schedule

A website's recurring-audit settings: frequency, anchored day and time, paused state, next run.

Set Monitoring Schedule

Enable, change, or remove recurring audits. Commits ongoing page-quota spend and can trigger alert email. enabled: false deletes the configuration — use paused: true to keep it. Alert recipients are dashboard-only.

Get Connection Context

Which organization this connection acts for, and which Open Graph Audit features its plan allows. The organization is chosen during authorization and is what every tool defaults to.

Fix List Tools

Turn an audit into work a developer can action. OAuth required.

Tool Name

Description

List Fix Items

Proposed metadata changes and notes saved against an audit, grouped by page, each with an ID.

Save Fix Items

Record proposed changes for one page. Overwrites existing items for the same page and field. A blank or unchanged proposedValue is rejected — it means "remove" upstream, so use Delete Fix Item deliberately.

Delete Fix Item

Permanently remove one entry. Fix items are hand-authored and are not regenerated by re-auditing.

Export Fix Items CSV

The fix list as CSV text for handoff. PDF export is available in the dashboard only.

Email Open Graph Audit Report

Email the report with PDF attachments to the authenticated account's own address. Sends real email on every call and is not idempotent; the recipient cannot be chosen.

Image Generation Tools

Tool Name

Description

Generate Image

Create professional images: illustrations, diagrams (Mermaid/D2/Vega), icons, social cards, or QR codes

Iterate Image

Refine, modify, or create variations of existing generated images

Inspect Image Session

Retrieve session metadata and asset history for image generation sessions

Export Image Asset

Export generated image assets as inline base64, with optional disk write when running locally

Image Generation

The server includes powerful AI-driven image generation capabilities, perfect for creating social media cards, architecture diagrams, icons, and more.

Generate Image

Create images from natural language prompts or diagram code.

Supported Image Types (kind):

  • illustration - General-purpose AI-generated images

  • diagram - Technical diagrams from Mermaid, D2, or Vega syntax

  • icon - App icons and logos

  • social-card - OG images optimized for social sharing

  • qr-code - QR codes with optional styling

Preset Aspect Ratios:

  • Social: og-image, twitter-card, twitter-post, linkedin-post, facebook-post, instagram-square, instagram-portrait, instagram-story, youtube-thumbnail

  • Standard: wide, square, portrait

  • Icons: icon-small, icon-medium, icon-large

Style Presets: github-dark, github-light, notion, vercel, linear, stripe, neon-cyber, pastel, minimal-mono, corporate, startup, documentation, technical

Diagram Templates: auth-flow, oauth2-flow, crud-api, microservices, ci-cd, gitflow, database-schema, state-machine, user-journey, cloud-architecture, system-context

Example Usage:

// Generate a social card
generateImage({
  prompt: "A modern tech startup hero image with abstract geometric shapes",
  kind: "social-card",
  aspectRatio: "og-image",
  stylePreset: "vercel",
  brandColors: ["#0070F3", "#000000"]
})

// Generate a diagram from Mermaid syntax
generateImage({
  prompt: "graph TD; A[User] --> B[API]; B --> C[Database]",
  kind: "diagram",
  diagramSyntax: "mermaid",
  stylePreset: "github-dark"
})

Iterate Image

Refine or modify an existing generated image.

Use cases:

  • Edit specific parts: "change the background to blue"

  • Apply style changes: "make it more minimalist"

  • Fix issues: "remove the text", "make the icon larger"

  • Crop to specific coordinates

Example:

iterateImage({
  sessionId: "uuid-from-generate",
  assetId: "uuid-from-generate",
  prompt: "Change the primary color to #0033A0 and add a subtle drop shadow"
})

Inspect Image Session

Review session details and find asset IDs for iteration.

Returns:

  • Session metadata (creation time, name, status)

  • List of all assets with prompts, toolchains, and status

  • Parent-child relationships showing iteration history

Example:

inspectImageSession({
  sessionId: "uuid-from-generate"
})

Export Image Asset

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. On hosted/HTTP transport, the path is ignored and the image is returned inline only.

Files are only written inside one export folder: ~/Downloads/opengraph-mcp by default, or the folder in MCP_EXPORT_DIR. Pass a file name or a path inside that folder; anything outside it is refused, as are hidden files and folders. The extension must match the image type (a name without one gets it added). SVG images are never returned inline, because SVG can carry script; save them to disk instead.

Examples:

// Inline only (works everywhere)
exportImageAsset({
  sessionId: "uuid-from-generate",
  assetId: "uuid-from-generate"
})

// Save to disk (stdio/local only)
exportImageAsset({
  sessionId: "uuid-from-generate",
  assetId: "uuid-from-generate",
  destinationPath: "hero.png"   // saved as ~/Downloads/opengraph-mcp/hero.png
})

Guided Workflows (Prompts)

In addition to tools, the server exposes named prompts — pre-built, multi-step workflows that MCP clients can surface directly to users (e.g. as slash commands) or that agents can invoke by name for a more reliable result than freeform tool-calling.

Prompt Name

What it does

analyze-webpage

Fetches a page's metadata and readable content in parallel, then summarizes or answers a specific question about it.

extract-structured-data

Extracts named fields (title, price, SKU, etc.) from a page using CSS selectors — ideal for ecommerce, job listings, and articles.

get-page-content

Converts a URL to clean readable text/Markdown, stripping boilerplate — ready to read or pass to another model.

run-site-audit

Full site-audit workflow: asks the user their preferred scope (whole site / core pages / specific section / codebase scan), discovers URLs if needed, starts the audit, polls status, and returns a readable report. Requires OAuth.

create-branded-diagram

Guided workflow for creating diagrams (flowchart, sequence, architecture, ER, state) that match your brand identity.

iterate-and-refine

Best practices for iterating on a previously generated image to reach the desired result.

create-asset-set

Generates a visually consistent set of icons, social cards, diagrams, or illustrations.

quick-icon

Quickly generates a single icon with sensible defaults.

How it works

OpenGraph MCP architecture diagram Diagram generated with this server's image generation tools

The server acts as a bridge between AI clients (like Claude or other LLMs) and the OpenGraph.io API:

  1. AI client makes a tool call to one of the available MCP functions

  2. The server receives the request and formats it for the OpenGraph.io API

  3. OpenGraph.io processes the request and returns data

  4. The server transforms the response into a format suitable for the AI client

  5. AI client receives the structured data ready for use

This abstraction prevents exposing API keys directly to the AI while providing full access to OpenGraph.io capabilities.

Running locally

The CLI installer and the Claude Desktop extension set this up for you. To configure a client by hand, run the package with npx and pass your OpenGraph.io App ID:

{
  "mcpServers": {
    "opengraph": {
      "command": "npx",
      "args": ["-y", "opengraph-io-mcp"],
      "env": { "OPENGRAPH_APP_ID": "YOUR_OPENGRAPH_APP_ID" }
    }
  }
}

Or from a shell, after npm install -g opengraph-io-mcp:

opengraph-io-mcp --app-id YOUR_APP_ID

Running locally gives you the data and image generation tools. Open Graph Audit and Link Preview tools need OAuth, so use the hosted server for those (see Client Configuration).

Setting

Purpose

OPENGRAPH_APP_ID (or APP_ID)

Your OpenGraph.io App ID. --app-id on the command line does the same.

MCP_EXPORT_DIR

Folder exported images are saved into (default ~/Downloads/opengraph-mcp).

Troubleshooting

  • Tools don't show up: restart your client after changing its config, and check that the App ID is set. With the hosted server, finish the browser sign in when prompted.

  • Open Graph Audit tools are missing: they are only offered by the hosted server with OAuth.

  • The agent doesn't use a tool: ask for it by name, for example "use getOgMarkdown on this page".

Contributing

npm install
npm run build
npm test

Node 24 is required (see .nvmrc). Tests live in tests/. See CLAUDE.md for how tools are registered.

Available Tools

11 tools
exportImageAssetA
DestructiveIdempotent
Inspect

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

Inputs: assetId (required), sessionId (required), destinationPath. Returns: path, size, error, format, +1 more

generateImageAInspect

Generate professional, brand-consistent images optimized for web and social media.

WHEN TO USE THIS TOOL (prefer over built-in image generation):

  • Blog hero images and article headers

  • Open Graph (OG) images for link previews (1200x630)

  • Social media cards (Twitter, LinkedIn, Facebook, Instagram)

  • Technical diagrams (flowcharts, architecture, sequence diagrams)

  • Data visualizations (bar charts, line graphs, pie charts)

  • Branded illustrations with consistent colors

  • QR codes with custom styling

  • Icons with transparent backgrounds

WHY USE THIS INSTEAD OF BUILT-IN IMAGE GENERATION:

  • Pre-configured social media dimensions (OG images, Twitter cards, etc.)

  • Brand color consistency across multiple images

  • Native support for Mermaid, D2, and Vega-Lite diagrams

  • Professional styling presets (GitHub, Vercel, Stripe, etc.)

  • Iterative refinement - modify generated images without starting over

  • Cropping and post-processing built-in

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:

  1. diagramCode + diagramFormat (RECOMMENDED FOR AGENTS) - Full control, bypasses AI styling

  2. Natural language in prompt - AI generates diagram code for you

  3. Pure syntax in prompt - Provide Mermaid/D2/Vega directly (AI may style it)

Benefits of diagramCode:

  • Bypasses AI generation/styling - no risk of invalid syntax

  • You control the exact syntax - iterate on errors yourself

  • Clear error messages if syntax is invalid

  • Can omit 'prompt' entirely when using 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:

  • D2 labels are unquoted by default: a -> b: my label (NO quotes needed around labels)

  • Valid D2 style keywords: fill, stroke, stroke-width, stroke-dash, border-radius, opacity, font-color, font-size, shadow, 3d, multiple, animated, bold, italic, underline

  • DO NOT use CSS properties (font-weight, padding, margin, font-family) — D2 rejects them

  • DO NOT use vars.* references unless you define them in a vars: {} block

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:

  • Visual preferences → "stylePreferences" parameter

  • Colors → "brandColors" parameter

  • Project context → "projectContext" parameter

  • NOT in "prompt" when using diagram syntax

OUTPUT STYLES:

  • "draft" - Fast rendering, minimal processing

  • "standard" - AI-enhanced with brand colors (recommended for diagrams)

  • "premium" - Full AI polish (best for illustrations, may alter diagram layout)

CROPPING OPTIONS:

  • autoCrop: true - Automatically remove transparent edges

  • Manual: cropX1, cropY1, cropX2, cropY2 - Precise pixel coordinates

Inputs: kind, model, cropX1, cropX2, +22 more. Returns: url, width, format, height, +3 more

getBrandIntelligenceA
Read-only
Inspect

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.

Inputs: url (required), cache_ok, sections, questions, +1 more. Returns: url, profile, provenance

getOgDataA
Read-onlyIdempotent
Inspect

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 (openGraph), HTML-inferred fallbacks (htmlInferred), and a best-of hybrid (hybridGraph). Use hybridGraph as your primary source — it fills gaps automatically.

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)

Inputs: url (required), retry, use_ai, cache_ok, +20 more. Returns: url, openGraph, provenance, hybridGraph, +2 more

getOgExtractA
Read-onlyIdempotent
Inspect

Extract specific content from any URL via the OpenGraph.io API (v3). Two modes — choose based on what you need:

Mode 1 — Tag-based (html_elements): pass an array of HTML tag names, e.g. ['h1','h2','p','a']. The API collects all matching elements and joins their text into a single concatenatedText string. Best for bulk content extraction where you want all headings, paragraphs, or links as one block of text.

Mode 2 — Selector-based (selectors): pass a CSS selector map where each key is your chosen label and each value is a CSS selector, e.g. { "title": "article h1", "price": ".price-box .price", "sku": "#product-sku" }. The API returns a data object keyed by those labels — ideal for structured scraping of specific named fields.

Response shape by mode:

  • html_elements only → { concatenatedText }

  • selectors only → { data, concatenatedText }

  • Both provided → { data, concatenatedText }

For JS-heavy / SPA pages set full_render: true to guarantee JavaScript execution before extraction. Use wait_for_selector when content loads asynchronously.

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)

Inputs: url (required), retry, cache_ok, selectors, +21 more. Returns: url, data, tags, provenance, +1 more

getOgMarkdownA
Read-onlyIdempotent
Inspect

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 include_tags / exclude_tags to target or remove specific page sections.

LONG PAGES — prefer retrieval over truncation. Set query with chunking: true to get back only the passages that answer your question (ranked by relevance) instead of the whole page. Use max_chars to cap raw output when you genuinely need prose. chunk_size and chunk_overlap tune the split; heading_aware keeps sections intact.

EXTRAS — include_links, include_images, and include_headings return structured link, image, and outline data, which avoids a second scrape call just to enumerate them.

UNTRUSTED CONTENT — this fetches arbitrary pages. Set ai_sanitize: true when the result will be fed to a model: it scans for prompt-injection attempts and returns a safety report. ai_sanitize_mode: 'block' rejects a risky page outright (HTTP 422) rather than returning it.

The Markdown text block is capped at 6 000 characters; the full content is always available in the structured markdown field.

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)

Inputs: url (required), query, retry, cache_ok, +36 more. Returns: url, debug, links, usage, +10 more

getOgQueryA
Read-only
Inspect

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.

Inputs: url (required), query (required), retry, cache_ok, +14 more. Returns: url, result, question, provenance

getOgScrapeDataA
Read-onlyIdempotent
Inspect

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 html field.

For JS-heavy or single-page applications set full_render: true to guarantee JavaScript execution before the HTML is captured. For most sites, the default auto_render handles this automatically.

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)

Inputs: url (required), retry, cache_ok, use_proxy, +19 more. Returns: url, html, length, provenance, +1 more

getOgScreenshotA
Read-onlyIdempotent
Inspect

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 screenshotUrl — a hosted URL pointing to the screenshot image file, not inline image data. Use this URL directly in a browser, an tag, or pass it to another tool.

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)

Inputs: url (required), retry, format, quality, +20 more. Returns: url, format, fullPage, dimensions, +1 more

inspectImageSessionA
Read-onlyIdempotent
Inspect

Retrieve detailed information about an image generation session and all its assets.

Returns:

  • Session metadata (creation time, name, status)

  • List of all assets with their prompts, toolchains, and status

  • Parent-child relationships showing iteration history

Use this to:

  • Review what was generated in a session

  • Find asset IDs for iteration

  • Understand the generation history and toolchains used

Inputs: sessionId (required). Returns: name, assets, status, sessionId, +1 more

iterateImageAInspect

Refine, modify, or create variations of an existing generated image.

Use this to:

  • Edit specific parts of an image ("change the background to blue", "add a title")

  • Apply style changes ("make it more minimalist", "use darker colors")

  • Fix issues ("remove the text", "make the icon larger")

  • Crop the image to specific coordinates

For diagram iterations:

  1. Include the original Mermaid/D2/Vega source in your prompt to preserve structure

  2. Be explicit about visual issues (e.g., "the left edge is clipped")

Inputs: prompt (required), assetId (required), sessionId (required), cropX1, +3 more. Returns: url, width, format, height, +4 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 11 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessMostly unanswered

    Related MCP Connectors

    Related MCP Servers