Shotbot Mcp

net.shotbotPublished by shotbot.netv2.0.1Updated Oct 25, 2026

Screenshot API for AI agents: capture any public URL as JPEG, PNG, WebP, AVIF, or PDF.

VerifiedSTDIODesktop onlyBrowser AutomationMedia & Design

Overview

AI-generated overview

Shotbot MCP lets an AI assistant capture any public URL as a JPEG, PNG, WebP, AVIF or PDF screenshot through the Shotbot screenshot API.

What you can do
Capture a public web page as an image or PDF in a chosen format (JPEG, PNG, WebP, AVIF, PDF).
When to use it
Useful when an assistant needs a rendered snapshot of a public web page, for example to archive a page, produce a PDF, or check how a site looks, rather than reading its HTML.
Requirements
Runs as a local process over stdio (npm package shotbot-mcp, so Node.js is needed). Requires a Shotbot API key supplied in the SHOTBOT_API_KEY environment variable; a free key can be obtained from the provider. Network access is needed to reach the Shotbot service and the target URLs.
Before you install
The required SHOTBOT_API_KEY is a secret and should be kept out of logs and shared configuration. Screenshot requests are sent to the third-party Shotbot service, which sees the URLs you ask it to capture. Only public URLs are intended; do not point it at internal or private addresses.

Installation

In SourceWeft

  1. Open Shotbot Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.0.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.