
CaptureKit
dev.capturekitPublished by capturekit.devOfficial publisherv0.1.0Updated Nov 7, 2026
Capture websites as PNG, JPEG, WebP or PDF, extract their content, or analyse them with AI.
Overview
CaptureKit's official MCP server: capture webpages as PNG, JPEG, WebP or PDF, extract page content, crawl HTML, and get AI analysis of sites.
- What you can do
- Capture webpages as PNG, JPEG, WebP or PDF for previews, QA, reporting and archiving
- Extract structured page data, metadata, links and HTML or Markdown in one request
- Fetch raw HTML without rendering for fast scraping, audits and monitoring
- Analyze a webpage with AI for summaries, value proposition, features, categories and use cases
- Check account usage and credit balance, plus engine or endpoint health for the last hour
- When to use it
- Useful when an assistant needs screenshots, PDFs or extracted page content of live websites, or quick AI summaries of a page, without setting up a headless browser. Also fits SEO, monitoring, indexing and archiving workflows.
- Requirements
- A CaptureKit account and API key, sent as the x-api-key header for the hosted endpoint or as CAPTUREKIT_API_KEY for the local stdio package. The local package needs Node.js 20 or newer (or Docker); the hosted server needs no install. Network access to CaptureKit.
Installation
In SourceWeft
- Open CaptureKit in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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.capturekit%2Fmcp/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"capturekit": {
"type": "http",
"url": "https://mcp.capturekit.dev/"
}
}
}README
CaptureKit MCP Server
Official Model Context Protocol server for the CaptureKit screenshot API.
Capture websites as PNG, JPEG, WebP or PDF, extract their content, or analyse them with AI.
It lets Claude, Cursor, VS Code, Windsurf and any MCP client call the API as tools. Runs over stdio (local) or Streamable HTTP (self-hosted).
Requirements
Hosted server (recommended)
CaptureKit runs this server for you at https://mcp.capturekit.dev/ (Streamable HTTP). Send your API key in the x-api-key header; nothing to install.
The hosted server and this package expose the same API; run the package locally when you want stdio, your own network egress, or to self-host it.
Run it locally
Claude Code
Claude Desktop, Cursor, Windsurf and other clients
Add the server to the client's MCP configuration (claude_desktop_config.json, .cursor/mcp.json…):
VS Code
Claude Desktop extension
Download the .mcpb bundle from the releases page and open it; Claude Desktop asks for your API key.
Docker
Tools
Every tool that calls the API consumes credits. JSON results are returned as text; images are returned inline and other files (PDF…) as embedded resources, up to 4 MB.
Streamable HTTP
The endpoint is POST /mcp (stateless, JSON responses). Each client sends its own key in the x-api-key header (or Authorization: Bearer <key>); the server never uses a key of its own. It binds to 127.0.0.1 by default and rejects browser origins unless you allow them — put it behind TLS before exposing it.
createHttpHandler() is exported for Fetch-compatible runtimes (Cloudflare Workers, Deno, Bun):
Security
- The API key is read from
CAPTUREKIT_API_KEY(stdio) or the request headers (HTTP) and removed from error messages. - Content fetched from websites is untrusted: the server instructions tell the model to treat it as data, not instructions.
- See SECURITY.md to report a vulnerability.
Development
Built on the SDK
The server uses the official Node.js SDK (@capturekitdev/sdk).
All CaptureKit SDKs
License
MIT — see LICENSE.
Source: README.md at commit d77503f
Tools
0Version history
1- v0.1.0LatestNov 7, 2026
Score
85% 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 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
- License10 pts