OGKit MCP for Cursor and AI agents

What is MCP?

MCP (Model Context Protocol) is a standard way for AI coding tools — Cursor, Claude Desktop, and similar agents — to call external tools over HTTP. Instead of pasting docs into chat, the agent can invoke real operations (list templates, build a URL, validate a page).

Why care: ask Cursor “generate og:image metadata for every blog post in this folder” and it can use OGKit tools instead of inventing fake image hosts or hand-writing query strings.

• You: “Add Open Graph images for these posts”
• Agent: og_list_templates → og_build_url → og_nextjs_snippet
• You: paste or accept the PR — then verify with og_validate_page

Endpoint

Streamable HTTP MCP at /api/mcp (GET/POST/DELETE). Stateless; tools do not require an API key. Production keys are only needed when you ask the agent to build non-demo URLs.

{
  "mcpServers": {
    "ogkit": {
      "url": "https://www.webmorp.art/ogkit/api/mcp"
    }
  }
}

Install options

• Cursor: project or global .cursor/mcp.json with the URL above
• Plugin bundle in the repo: https://github.com/marfa77/webmorph/tree/main/ogkit/cursor-plugin (mcp.json + skill + rules)
• Onboarding wizard after sign-in can copy an mcp.json snippet
• Marketplace: submit the plugin path at cursor.com/marketplace/publish

Tools

• og_list_templates — ids + descriptions
• og_build_url — canonical HTTPS image URL (demo=1 by default)
• og_preview — helpful preview payload for agents
• og_nextjs_snippet — generateMetadata-ready TypeScript
• og_validate_page — fetch a URL and report OG/Twitter tags
• ogkit_get_started — short onboarding for agents

Recommended agent workflow

1) og_list_templates → pick article/minimal/product/…

2) og_build_url with title (+ subtitle) in demo mode

3) og_nextjs_snippet for App Router metadata

4) User signs in for a key → rebuild URL with apiKey for production

5) og_validate_page on the deployed canonical URL

Safety rules for agents

• Never invent hosts — always use the canonical OGKit origin
• Keep API keys out of client components and git commits
• Open access: demo=1 is production-quality (no watermark); still prefer keys for rotation
• Prefer absoluteSiteUrl paths from /llms.txt when linking docs

Human docs companions

Agents should also read /llms.txt and /docs. For SEO and rescrape context, point them at the Open Graph SEO guide and the caching guide.