site-shot/site-shot-mcp

Give Claude, Cursor, and other AI agents the ability to **see public web pages** — take website screenshots
with Site-Shot over the Model Context Protocol.
Real Chromium rendering · full-page capture · country proxies · automatic **ad & cookie-banner removal**
(cleaner images, fewer vision tokens).
A Site-Shot API key is required, and it takes a paid Site-Shot API plan: captures draw on that
account's existing API allowance and limits. The key comes from your
Site-Shot dashboard; pricing
lists the plans. The no-signup browser tool at is for checking output
quality; it does not issue keys.
Claude Code (plugin)
This repository doubles as a Claude Code plugin marketplace. The plugin runs the published
site-shot-mcp package over stdio and declares the API key as a required sensitive setting, so
Claude Code prompts you for it rather than asking you to paste it into this repository, a config
file, or a chat message.
Install
or from inside a session:
Both forms resolve the marketplace from GitHub, so they work only after these manifests are
published on the repository's public default branch — not from a local branch or a fork you
have not pushed.
Try it before that
Load the plugin directory for a single session:
Two things matter here. Pass an **absolute** path — --plugin-dir is resolved against the session's
working directory. And start that session from an ordinary project directory, **not from this
checkout**: this repo *is* the site-shot-mcp package, so npm resolves the name locally, finds no
linked binary, and the server dies with sh: site-shot-mcp: command not found before Claude Code
ever sees it. From an unrelated directory npx fetches the published package and starts it
normally — checked both ways: exit 127 in this checkout, clean stdio start from an empty one.
To exercise the real install path instead — marketplace resolution, manifests and the required
setting — add the checkout itself as a marketplace:
That installs into your user scope; undo it with claude plugin uninstall site-shot@site-shot and
claude plugin marketplace remove site-shot.
The API key
The plugin declares SITESHOT_API_KEY as a required, sensitive setting. Claude Code prompts you for
the key, masks it as you type, and substitutes it into the server's environment as
${user_config.SITESHOT_API_KEY}. Storage of the value is Claude Code's to handle.
Installing without one is not an error — Claude Code records it as still owed
(1 userConfig option not yet set (1 required)). Supply it through the masked prompt:
Configure it before expecting a capture: that setting is what feeds the server its key. What Claude
Code does while it is unset — whether the server is launched at all, whether the tools are offered —
is Claude Code's own behaviour and is not something documented here from observation.
The server's side is independent of that. When run directly over stdio **without a key**, it still
starts and prints a warning on stderr. Capture tools return a clear missing-key error instead of an image.
The plugin adds one skill (site-shot:website-screenshots) and the two capture tools
below. It declares no hooks, no monitors and no scheduled capture jobs; the only process
it launches is the declared stdio MCP server.
Codex CLI (plugin)
This repository is also a Codex plugin marketplace. It installs the same plugin directory as Claude
Code does — one shared skill, the same pinned site-shot-mcp@1.2.0 over stdio — with its own
manifest, because the two hosts wire the credential differently.
Install
Exercised against Codex CLI 0.147.0 on macOS (arm64). As with Claude Code, these resolve the
marketplace from GitHub, so they work only once these manifests are on the public default branch;
before that, point codex plugin marketplace add at a local checkout path instead.