CaptureKit MCP updated to the 2026-07-28 spec

Our MCP server now supports the MCP 2026-07-28 specification. Same tools for screenshots, content extraction, and crawling, ready for Claude and other MCP clients.
We updated the CaptureKit MCP server to the MCP 2026-07-28 specification.
This version of the protocol moves to a stateless request/response core, tightens authorization, and introduces a formal extensions framework. Our server is ready for Claude and other MCP clients as they roll out support.
Nothing changes on your side for day-to-day use. You still get screenshots, content extraction, Markdown, and crawling at https://mcp.capturekit.dev/.
Quick setup
Cursor (Settings → MCP):
{
"mcpServers": {
"capturekit": {
"url": "https://mcp.capturekit.dev/",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}
Claude Code:
claude mcp add --transport http capturekit https://mcp.capturekit.dev/ --header "x-api-key: YOUR_API_KEY"
Full configuration details are in the MCP docs.
Ready to get started with CaptureKit?
Start capturing screenshots and extracting content today. Get started for free.
Get StartedYou Might Also Like
Automate Website Screenshots using n8n & CaptureKit Website Capture API
Learn how to build a powerful automation workflow that captures screenshots of websites at scale using n8n, Google Sheets, and CaptureKit/'s Screenshot API.
Sitemap Support, Zapier integration, and Storage Flexibility
Learn about new features in CaptureKit based on user feedback: sitemap extraction, Zapier integration for no-code automation, and storage endpoint support.
CaptureKit is moving to a new dashboard
We are migrating CaptureKit to a new platform at app.capturekit.dev. Learn what changes, what stays the same, and how to migrate your API calls.