List and inspect ordered sessions.
list_capture_sets and get_capture_set expose manifest metadata, capture order, sizes, and checksums.
SCREENSHOT MCP SERVER LOCAL BETA
Make visual contextreadable through MCP.
ScreenCrate’s local MCP server reads only an approved capture workspace. Compatible clients can request ordered sets, original images, element context, design tokens, assets, and bounded component exports—without turning the browser into a remote-control surface.
- Local stdio server
- Read-only workspace
- Checksummed files
AN EXPLICIT LOCAL HANDOFF
- 01Approve export
- 02Bind workspace
- 03Read through MCP
01 / MCP TOOL SURFACE
Visual resources with specific, inspectable tools.
The server does not expose an open-ended filesystem or browser-automation command. Each tool returns a bounded part of a ScreenCrate bundle under a strict local workspace root.
Read one approved image at a time.
get_capture_image validates the path, file signature, declared MIME type, checksum, and configured bounds.
Request element context, tokens, or assets.
get_element_context, get_design_tokens, and get_assets return only data present in the approved bundle.
Read generated component artifacts.
export_component returns sanitized, size-limited export material already contained in the bundle; the server does not execute generated code.
02 / DATA PATH
You choose the set. The client reads the boundary.
An extension cannot act as a conventional local stdio MCP process by itself. ScreenCrate separates browser capture, explicit local export, and the Node-based MCP server so each trust boundary is visible.
{
"captureSet": "design-review",
"images": 6,
"context": "selected-element",
"workspace": "approved",
"transport": "stdio"
}
tools:
- list_capture_sets
- get_capture_image
- get_element_context
- get_design_tokens03 / SECURITY BOUNDARIES
MCP access should be narrow and reviewable.
The beta validates manifests and files before returning them. It rejects traversal, symlink escapes, unsupported signatures, oversized records, and malformed JSON.
Approved local workspaceSUPPORTED
The server is configured with a strict ScreenCrate workspace root and reads valid capture bundles inside it.
Compatible MCP clientsBETA
Client configuration differs by host. A verified compatibility matrix will follow real integration tests.
Live browser automationNOT INCLUDED
This is a screenshot-context MCP server, not a generic browser MCP for navigation, clicking, or form submission.
Hosted cloud endpointNOT AVAILABLE
The current server runs locally over stdio. ScreenCrate does not claim a public remote connector or hosted endpoint.
04 / FAQ
Screenshot MCP, precisely.
Does MCP automatically insert screenshots into ChatGPT or Claude?
No. MCP clients can request registered tools and resources. Browser-chat attachments use separate extension adapters and still require user review.
Can the MCP server browse or control websites?
No. It reads approved ScreenCrate bundles. It does not navigate, click, type, submit forms, or control the browser.
Does it upload my capture set to ScreenCrate?
No hosted endpoint is required for the current local stdio server. Your chosen MCP client may have its own data policy, which you should review separately.
Is the MCP package publicly installable?
Not yet. The server is implemented for repository-based beta testing; public package and verified client setup instructions remain pending.
Give compatible clients approved visual context.
Keep capture and local MCP access separate, explicit, and inspectable. Request the beta to test the repository-based server with your workflow.