ForgeKit

dev.useforgekitPublished by useforgekit.devOfficial publisherv1.1.0Updated Oct 27, 2026

Developer utility MCP: screenshots, PDFs, OG, QR, link preview, JSON validate, ShipPack.

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Remote MCP server giving assistants developer utilities such as screenshots, PDFs, OG images, QR codes, link previews, JSON validation and ShipPack.

What you can do
  • Generate screenshots and PDFs from web pages or content
  • Create Open Graph images, QR codes and link previews
  • Validate JSON
  • Produce ShipPack output
  • All capabilities are reached through a single hosted endpoint rather than a local package
When to use it
Useful when an assistant needs to produce visual or document artifacts (screenshots, PDFs, social images, QR codes) or check JSON while working on a project, without installing local tooling.
Requirements
A remote MCP endpoint at useforgekit.dev over streamable HTTP. A bearer token is required in the Authorization header; the manifest also mentions API key or x402 payment headers. No environment variables or local packages are declared.
Before you install
The Authorization header carries a live-looking secret (fk_live_ prefix) and must be kept private. The manifest mentions x402 payment headers, so some usage may involve paying. Content sent for screenshots, PDFs or previews is processed by a third-party service.

Installation

In SourceWeft

  1. Open ForgeKit in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/dev.useforgekit%2Fforgekit/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": {
    "forgekit": {
      "type": "http",
      "url": "https://useforgekit.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

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

Version history

1
  1. v1.1.0LatestSep 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.