Slimsnap

Name: Slimsnap
Author: bickov

by bickovversion 0.1.2i★ –iRuns on your computer

Registry nameio.github.bickov/slimsnap

Install

Overview

Description from the maker (original English)

Your recent screen captures as structured JSON your AI agent can read. Local only, no network.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "slimsnap": {
      "command": "npx",
      "args": [
        "-y",
        "@slimsnap/mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add slimsnap -- npx -y @slimsnap/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "slimsnap": {
      "command": "npx",
      "args": [
        "-y",
        "@slimsnap/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "slimsnap": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@slimsnap/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account bickov, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32606 servers in this category
Published to the registry more recently than 20% of the other 32606 servers in this category
Basic checks equal to or better than 100% of the other 32606 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Slimsnap safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Georgia MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Georgia MCP

by abgeo

An MCP server for Georgian public data, read from the organizations that publish it.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

SlimSnap connector

Your recent screen captures, as structured data your AI can actually read.

Take a capture in SlimSnap, mark what you mean, then in Claude or Cursor say "look at my last capture". No pasting, no file paths, no clipboard.

What your agent gets

Not a screenshot. A JSON document: every piece of text on screen with its position and colour, plus the arrows, boxes and callouts you drew, and which element each one points at.

That matters for three reasons.

A screenshot pasted into an agent gets downscaled before the model reads it, and nobody tells you. Anthropic's own docs say to pre-resize and crop your images because resizing "might make text less legible". A tall page loses its text entirely.

Images returned over MCP are worse still. In Claude Code they are passed through as text rather than native image blocks, costing roughly 15-25k tokens against about 1.6k for the same image pasted directly, and the model cannot read them at all (claude-code#31208, closed as not planned). A big enough result blows the per-result token ceiling outright (#9152).

And an oversized screenshot can poison a session permanently. It stays in context, gets re-sent every turn, and there is no way to remove it (#55040).

This connector sidesteps all three by never sending the picture. An ordinary screen costs roughly a third less than the same screen as an image, and on a tall page the comparison stops being about cost at all: shrinking an 18,410 pixel page to fit the model's 1568 pixel limit leaves body text 1.4 pixels tall, so the cheap image is cheap because it is unreadable. Either way the agent gets exact coordinates rather than a guess about which button you meant.

When you genuinely need pixels (visual style, spacing, colour balance) there is a separate tool for that, and the image is already downscaled to a size the model can read.

Install

Claude Code

claude mcp add slimsnap -- npx -y @slimsnap/mcp

Then check it: /mcp should list slimsnap with 4 tools.

Claude Desktop

Download slimsnap-mcp.mcpb from Releases and open it. Claude shows an install dialog. The connector then appears under Settings.

Cursor

Or add it by hand to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project:

"mcpServers": { "slimsnap": { "type": "stdio", "command": "npx", "args": ["-y", "@slimsnap/mcp"] } } }

Project config wins over global when both exist. Then ask Cursor about your last capture the same way you would ask Claude.

As a Claude Code plugin (same connector, installed and updated as a plugin)

/plugin marketplace add bickov/slimsnap-mcp

/plugin install slimsnap@slimsnap

You need SlimSnap 0.5.0 or newer, because that is the version that started keeping recent captures on disk.

Approving the tools

The first time Claude Code uses each tool it asks for permission, and the approval is scoped to the folder you were in. Four tools means four prompts, and they come back in the next project. Nothing is wrong; that is how Claude Code gates MCP tools.

To approve them once, everywhere, add this to ~/.claude/settings.json:

"permissions": { "allow": [ "mcpslimsnapget_latest_capture", "mcpslimsnaplist_captures", "mcpslimsnapget_capture", "mcpslimsnapget_capture_image" ] } }

If the file already exists, merge the allow entries into it rather than replacing it. Restart Claude Code afterwards.

Tools

Tool	What it does
`get_latest_capture`	The newest capture as structured JSON. This is the one that gets used most.
`list_captures`	Recent captures newest first, with a text preview. Use it to find an older one, or to work through several marked screens at once.
`get_capture`	One capture by id.
`get_capture_image`	One frame as a downscaled image, for when the JSON cannot answer the question.

Four tools on purpose. Tool descriptions are charged against your context window on every turn, so the surface stays small.

See a real capture

Two sample captures live in samples/ — one single screen, one three-frame scroll capture, both with an arrow resolved to the element it points at. Copy either into ~/.slimsnap/recent/ and the connector will read it, so you can try all four tools before installing SlimSnap.

mkdir -p ~/.slimsnap/recent

cp -R samples/single-frame ~/.slimsnap/recent/2026-07-30T09-00-00-000000-00-00

Then ask your agent *what did I mark in my last capture?* — it should come back with the Save changes button and the note attached to it.

Where the data lives

SlimSnap keeps your recent captures in ~/.slimsnap/recent/, newest 20 by default. Each capture is a folder with capture.json, a small meta.json index, and one PNG per frame capped at 1568px on the long edge.

The connector finds that folder by reading ~/.slimsnap/config.json, which SlimSnap rewrites whenever your settings change. Move your save folder and the connector follows, with nothing to reconfigure.

Change how many are kept, or turn the cache off entirely, in SlimSnap under Settings, Export, Recent captures. There is a Clear button in the same place.

Privacy Policy

The server reads files under your home directory and talks to nobody. There is no network code in it. It cannot capture your screen and it cannot ask SlimSnap to capture your screen. It only reads captures you already took and chose to keep.

Nothing is uploaded, there is no account, and no telemetry.

No personal data is collected, stored, transmitted or shared. The server has no network code and no analytics. Full policy: https://slimsnap.ai/privacy.

Requirements

SlimSnap 0.5.0 or newer, macOS or Windows. Works with Claude Code, Claude Desktop and Cursor.

Codex is not supported yet. It caps a single tool result at about 10 KB, which a real capture goes past, and it drops image content when structured output is present (codex#7906, #10334). Both are open upstream.

The Claude Desktop route needs nothing else: Desktop ships its own Node and the .mcpb bundle uses it. The Claude Code route runs node from your PATH, so it needs Node 18 or newer installed. That catches people out on a fresh Windows machine, where Node usually isn't there.

License

MIT

Slimsnap

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Georgia MCP

README from the maker

SlimSnap connector

What your agent gets

Install

Approving the tools

Tools

See a real capture

Where the data lives

Privacy Policy

Requirements

License