SCREENSHOT MCP SERVER LOCAL + DIRECT

Connect screenshots to AI clientswith MCP.

Choose a local stdio server that reads an approved workspace, or Direct MCP over authenticated HTTPS for Pro. Both paths expose ordered images and bounded webpage context through the same read-only tool surface—not general browser control.

Open the setup guide →Compare both paths ↓

Local stdio option
Direct MCP for Pro
Seven read-only tools

Framnova capture set exported to a bounded local workspace and read by a compatible MCP client — **EXPORT**USER APPROVALVALIDATEBOUNDED WORKSPACEREADMCP TOOLS

7 read-only toolsSTRICT INPUT SCHEMASOne approved setMANIFEST + SHA-256

TWO EXPLICIT HANDOFF PATHS

01Approve a set
02Export or sync
03Read through MCP

01 / MCP TOOL SURFACE

Visual resources with specific, inspectable tools.

Neither server exposes an open-ended filesystem or browser-automation command. Each tool returns a bounded part of a validated Framnova capture bundle.

CAPTURE SETS

List and inspect ordered sessions.

list_capture_sets and get_capture_set expose manifest metadata, capture order, sizes, and checksums.

ORIGINAL IMAGES

Read one approved image at a time.

get_capture_image validates the path, file signature, declared MIME type, checksum, and configured bounds.

WEB CONTEXT

Request element context, tokens, or assets.

get_element_context, get_design_tokens, and get_assets return only data present in the approved bundle.

BOUNDED EXPORT

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 / TWO DATA PATHS

You choose the set. You choose where it lives.

Local MCP uses an explicit folder export and a Node-based stdio process. Direct MCP uses the extension’s explicit Sync action, private token-scoped storage, and authenticated Streamable HTTP. Capture alone starts neither handoff.

Local Framnova MCP data path from capture bundle to a compatible client

capture-set.jsonREAD-ONLY RESOURCE

{
  "captureSet": "design-review",
  "images": 6,
  "context": "selected-element",
  "workspace": "approved",
  "transport": "stdio | https"
}

shared tools:
  - list_capture_sets
  - get_capture_image
  - get_element_context
  - get_design_tokens

03 / SECURITY BOUNDARIES

MCP access should be narrow and reviewable.

Both paths validate manifests and declared files before returning them. The local server constrains paths to an approved root; Direct MCP constrains every request to the capture sets authorized by one bearer token.

Local stdio MCPSUPPORTED

A Node process reads valid bundles inside one approved Framnova workspace. It does not upload them.

Direct MCP over HTTPSPRO

The extension uploads only after explicit Sync, and clients authenticate to https://mcp.framnova.com/mcp with the same Pro token.

Live browser automationNOT INCLUDED

This is a screenshot-context MCP server, not a generic browser MCP for navigation, clicking, or form submission.

Claude Desktop remote connectorOAUTH NEXT

The current Direct MCP path uses bearer authentication. Claude Desktop’s remote connector path requires a separate OAuth implementation.

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 Framnova bundles. It does not navigate, click, type, submit forms, or control the browser.

Does it upload my capture set to Framnova?

Local MCP does not. Direct MCP uploads one approved set only after you choose Sync to Direct MCP. Your chosen client and model provider may have separate data policies, which you should review.

Is the local MCP package publicly installable?

The local server currently runs from the repository build. Direct MCP does not require that local package; it uses the authenticated HTTPS endpoint.

Give compatible clients approved visual context.

Keep capture and MCP access separate, explicit, and inspectable. Choose local stdio for a folder on your machine or Direct MCP for one authenticated Pro connection.

Connect MCP →