LOCAL REPOSITORY BETA

The local MCP server is implemented for repository testing. No public package or hosted endpoint is available yet.

Request beta
VISUAL CONTEXT FOR MCP CLIENTS LOCAL BETA

Your captures. Approved by you. A bounded local MCP beta.

ScreenCrate's local server reads an explicitly exported workspace, validates its manifests, and offers bounded resources to a compatible MCP client you configure.

Request MCP beta See the local beta flow
SCREENCRATE MCP · WORKFLOW PREVIEW ILLUSTRATIVE UI
Illustrative ScreenCrate MCP beta interface showing a user-approved capture session shared through a local connector to an AI coding client.
Illustrative UI for the repository beta; the final interface may change. 1586 × 992 · LOCAL BETA PREVIEW
  1. 01
    Bind one session

    The client does not automatically receive your entire library.

  2. 02
    Approve locally

    Review images and context before exposing resources.

  3. 03
    Retrieve through MCP

    A compatible client requests only the session or resource it needs.

01LOCAL BETA FLOW

One explicit path. No ambient access.

The repository beta is built around visible decisions: export an approved set, configure a strict local root, and connect a compatible MCP client.

  1. 01 SESSION

    Choose the capture set.

    One session preserves originals, order, notes, and any selected Code Context.

    Nothing bound yet
  2. 02 LOCAL APPROVAL

    Review exactly what will be exposed.

    The planned connector shows the client, session, and resource list before access is authorized.

    Explicit action required
  3. 03 MCP RETRIEVAL

    The client requests the bound resource.

    The session, one screenshot, or its context can be retrieved through a narrow interface.

    Approved scope only
MCP is not a universal browser-chat attachment API.

Compatible clients can request MCP tools and resources. To insert files into ChatGPT, Claude, Gemini, Grok, or Perplexity in the browser, ScreenCrate uses separate extension adapters.

See the extension↗
02LOCAL APPROVAL

The client asks. You decide.

The goal of the local connector is to keep the approval moment on your device. A request should not become access until you can see its scope.

Repository-beta behavior; subject to ongoing security testing.
01
Client identity is visible

The request identifies which configured client wants the session.

02
Resource list before approval

Images, notes, and page context appear as separate resources.

03
Scoped binding

Approval applies to the selected session, not every future capture.

04
Clear unbinding

The specification includes a visible way to remove local access.

03RESOURCE BINDING

One session. Addressable resources.

The session is the container; each capture and context block keeps its own identity. A client can request the manifest or one specific resource.

capture-session-042SPEC DRAFT
screencrate://sessions/capture-session-042
  • IMG
    01-landing-direction.pngOriginal capture · order 01
    BOUND
  • IMG
    02-mobile-state.pngOriginal capture · order 02
    BOUND
  • CTX
    page-context.jsonSelected structure, text, and tokens
    OPTIONAL
  • TXT
    session-note.txtUser prompt and annotations
    BOUND
04COMPATIBLE CLIENTS

Compatible by capability. Verified before promised.

ScreenCrate targets MCP hosts that can invoke tools and read resources. We will publish a verified client list after beta testing—not before.

RREQUIRED

Resource reading

The client can open images and structured data returned by the connector.

TREQUIRED

Tool invocation

The client can list sessions and request a screenshot or bundle by ID.

LFIRST BETA

Local transport

The first target is a configured client on the same device as the connector.

Compatibility is not certified yet. MCP implementations vary between clients. A public matrix will be added after we validate tools, resources, image sizes, and permission behavior end to end.

05REPOSITORY BETA SURFACE

Small on purpose. Implemented and bounded.

These seven tools match the current local server. Their schemas may evolve before any public distribution.

BETA TOOLPURPOSESTATUS
list_capture_sets

List metadata for valid capture sets in the workspace.

BETA
get_capture_set

Return a capture-set manifest, order, and resource references.

BETA
get_capture_image

Read one validated original image from the approved set.

BETA
get_element_context

Retrieve bounded selected-element context when included.

BETA
get_design_tokens

Return observed color, typography, spacing, and related tokens.

BETA
get_assets

Return approved asset references from the manifest.

BETA
export_component

Read sanitized, bounded export artifacts included in the bundle.

BETA
06CONNECTION BOUNDARIES

Local beta first. No hosted endpoint.

The repository server runs locally over stdio. There is no public package, verified client matrix, or remote sync yet.

LOCAL REPOSITORY BETA LOCAL SERVER

Local capture sets for clients you configure.

The server validates and reads bundles inside a strict local root; it does not pull captures directly from tabs or the browser queue.

  • ✓No permanent public URL
  • ✓Per-session approval
  • ✓Explicitly configured client
PLANNED · NOT AVAILABLE HOSTED ENDPOINT

A future option for remote and team workflows.

It will only be considered after validating permissions, revocable credentials, encryption, retention, and deletion controls.

  • —Explicit session upload
  • —Scoped credentials
  • —Retention controls
07MCP QUESTIONS

Before binding a session.

Straight answers about the repository beta and what is not publicly available yet.

Can I install the MCP connector today?

The beta can run from the repository, but there is no public package, one-command install, or hosted endpoint yet.

What does local approval mean?

You explicitly export a bundle to a directory you choose and configure the server with that local root. It does not read the browser queue ambiently.

Which AI clients will be compatible?

The target is MCP hosts that support tools, resources, and images. We will publish names only after verifying the complete flow with each client.

Will MCP inject attachments into any browser chat?

Not universally. Browser-chat attachments still depend on platform-specific extension adapters; MCP is a separate path for compatible clients.

Is my entire capture library shared?

No. The server only sees valid bundles inside the local root you configure. It has no ambient access to tabs, history, or the extension queue.

Does Code Context copy an entire site?

No. It is designed to add rendered structure, text, and styles from the area you selected. You remain responsible for permission to capture and share that content.

08MCP REPOSITORY BETA

Help us validate the right boundary.

We are looking for people who work with multi-screen captures, local MCP clients, and product, support, or development tasks.

  • ✓Early testing of the local approval flow
  • ✓Shape resources, tools, and permissions
  • ✓No general-availability promise yet
BETA REQUESTTell us how you would use MCP.

Form preview: delivery will be connected before beta opens.