claude mcp add opengraph-io-mcp -- npx -y opengraph-io-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
2 ★ · securecoders/opengraph-io-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 2 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository securecoders/opengraph-io-mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
og‑mcp is a Model‑Context‑Protocol (MCP) server that makes every OpenGraph.io ( https://opengraph.io ) API endpoint available to AI agents (e.g. Anthropic Claude, Cursor, 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: Quick Install CLI Installer (Recommended) The easiest way to configure OpenGraph MCP for any supported client: Supported clients: cursor, claude-desktop, windsurf, vscode, zed, jetbrains Claude Desktop Extension For Claude Desktop users, you can also download the .mcpb extension for one-click installation from the Releases page. Authentication The hosted MCP server supports two authentication methods: Option 1 — OAuth 2.1 (recommended for hosted deployments) OAuth lets you authorize access through your OpenGraph.io dashboard without copying API keys into config files. The MCP client handles the entire browser login flow automatically. **Supported by:** MCP clients that implement the Authorization Code + PKCE flow (Cursor, Claude Desktop 0.10+, VS Code with the MCP extension). When the client connects with no credentials, the server returns 401 with a WWW-Authenticate header pointing to: The client then fetches the authorization server metadata and starts the PKCE flow, redirecting your browser to https://dashboard.opengraph.io/oauth/consent where you log in and choose which API key to authorize. **No client-side config needed** — the client discovers everything automatically. Option 2 — x-app-id header (legacy / local dev) Pass your App ID as an HTTP header. Suitable for local dev, CI, or clients that do not support OAuth. Replace YOUR_OPENGRAPH_APP_ID with your OpenGraph.io App ID. --- Client Configuration All configurations below use the hosted HTTPS transport. OAuth is the recommended approach for shared/production use; the x-app-id header config is provided as a fallback. OAuth (no static config needed) For clients that support OAuth discovery, simply point at the hosted URL with no headers — the server will request authorization automatically: x-app-id fallback If your client does not support OAuth, or you prefer static config: Claude Desktop Config location: - **macOS**: ~/Library/Application Support/Claude/claude_desktop_config.json - **Windows**: %APPDATA%\Claude\claude_desktop_config.json Claude Code One-command installation: Cursor Config location: ~/.cursor/mcp.json VS Code Config location: .vscode/mcp.json (in your project directory) VS Code supports input prompts for secure credential handling: Windsurf Config location: ~/.codeium/windsurf/mcp_config.json JetBrains AI Assistant Add to your JetBrains AI Assistant MCP configuration: Zed Config location: ~/.config/zed/settings.json Note: Zed uses context_servers instead of mcpServers: Available Tools > **Two authentication tiers:** Data and Image Generation tools work with either OAuth or a simple x-app-id API key — including the stdio transport and the Claude Desktop extension. Site Audit and Link Preview tools require OAuth (hosted HTTPS transport only), since they bill against your organization's Site Audit 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 and extract tools use v1.1 (see notes). | Tool Name | API Endpoint | Description | Documentation | |-----------|--------------|-------------|---------------| | **Get OG Data** | /api/3.0/site/ | 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/ | Scrape raw HTML with full v3 rendering options including scroll-to-bottom, load-more clicks, and AI sanitization. | Docs |