SnapOG OG Image Generator

com.snapogPublished by snapog.comOfficial publisherv1.0.1Updated Oct 24, 2026

Give agents instant OG image generation, social metadata audits, and rendering guidance.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingMedia & Design

Overview

AI-generated overview

A remote MCP server that lets an assistant generate OG images, audit social metadata, and get rendering guidance.

What you can do
Generate OG images for pages or content on demand, so links render with a proper preview card when shared. Audit social metadata to check how a page's title, description and image tags will appear on social platforms. Provide rendering guidance to help an assistant produce or adjust OG image output. No individual tools are listed, so the exact operations are not documented.
When to use it
Useful when publishing pages or content and you want an assistant to create share preview images, check social metadata before launch, or get advice on rendering OG images correctly.
Requirements
A remote MCP endpoint at snapog.com, reached over streamable HTTP. No authentication, environment variables or headers are declared, and no local package is needed.
Before you install
The server is hosted by a third party, so content submitted for image generation or metadata auditing is sent to that service. No authentication is declared, so do not assume requests are private or tied to an account. Tool-level behavior is undocumented; review what it does before relying on it in publishing workflows.

Installation

In SourceWeft

  1. Open SnapOG OG Image Generator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.snapog%2Fsnapog/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "snapog-og-image-generator": {
      "type": "http",
      "url": "https://snapog.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.