OpenGraph.io MCP Server

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

Quick Install

CLI Installer (Recommended)

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.

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

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.

Open Graph Audit & Link Preview Tools

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.

Monitoring & History Tools

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

| Set Monitoring Schedule | Enable, chan