Snipper Mcp

io.github.teologovPublished by GitHub account teologovv1.0.0Updated Oct 24, 2026

Search, read, create and organise code snippets in SnipperApp 3, a native macOS snippet manager.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local MCP server bundled in SnipperApp 3 on macOS that lets an assistant search, read, create and organise your code snippets.

What you can do
Search, read, create, update and delete snippets in your SnipperApp library, including importing from the public Hub and searching it by keyword or ID. Create, rename and delete folders, and list workspaces, storages, groups and languages to see how the library is organised. List, add and remove tags on snippets, and create or delete tags. List, fetch, add and delete attachments on snippets.
When to use it
Use it when you keep code snippets in SnipperApp 3 on a Mac and want an assistant to find a saved helper, save a function you just wrote into a workspace and folder, or filter snippets by tag or language.
Requirements
macOS 15 or later (Apple Silicon or Intel) with SnipperApp 3 installed; the server is a stdio binary inside the app, so nothing else is installed. Add it by pointing the client at the app's snipper-mcp executable, or install the MCPB bundle in Claude Desktop. No API keys or environment variables are declared.
Before you install
The server writes to the same local SQLite database as the app, so created, updated and deleted snippets, folders, tags and attachments change your real library immediately; delete and untag tools are marked destructive. The three Hub tools call the public SnipperApp Hub API and send search terms or a snippet ID, though no library content is uploaded. Snippets can leave the machine only through sync storage you enable yourself, such as iCloud or GitHub Gist.

Installation

In SourceWeft

  1. Open Snipper Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

snipper-mcp — the MCP server inside SnipperApp 3

[SnipperApp 3 — code snippet manager for macOS]

SnipperApp 3 is a native macOS code snippet manager. It ships its own Model Context Protocol server, so AI assistants can search, read, create and organise the snippets in your library. There is nothing to install: the server is a stdio binary bundled in the app.

This repository documents the server's interface. The server itself is part of the app (Swift, built on the Swift MCP SDK).

Requirements

Install in Claude Desktop (one click)

Download snipperapp-1.0.2.mcpb from the latest release and open it; Claude Desktop installs it as an extension. The bundle contains only a small launcher (mcpb/server/index.js) that finds the server inside SnipperApp 3 and hands over stdio. Without the app it still answers initialize and tools/list (the manifest in mcpb/server/tools.json), and every tool call returns a clear not-installed error; a Dockerfile runs that mode for registry introspection checks.

Setup (manual)

Claude Code:

bash
claude mcp add snipper -- "/Applications/SnipperApp 3.app/Contents/MacOS/snipper-mcp"

Claude Desktop, Cursor (.cursor/mcp.json), Windsurf (~/.codeium/windsurf/mcp_config.json):

json
{  "mcpServers": {    "snipper": {      "command": "/Applications/SnipperApp 3.app/Contents/MacOS/snipper-mcp"    }  }}

Full guide: https://snipperapp.com/docs/mcp-integration

Tools (25)

AreaTools
Snippetssearch_snippets, get_snippet, create_snippet, update_snippet, delete_snippet
Folderslist_folders, create_folder, update_folder, delete_folder
Tagslist_tags, create_tag, delete_tag, add_tag_to_snippet, remove_tag_from_snippet
Attachmentslist_attachments, get_attachment, create_attachment, delete_attachment
Organisationlist_workspaces, list_storages, list_groups, list_languages
Hub (public snippets)search_hub, get_hub_snippet, import_from_hub

Every tool carries a title and the MCP annotations clients use to decide what needs confirmation: the twelve read tools are marked readOnlyHint, the five delete/untag tools destructiveHint, and the three Hub tools openWorldHint.

The server reads and writes the same local SQLite database as the app, so anything an assistant saves appears in SnipperApp immediately. Nothing is sent to a server; the Hub tools call the public Hub API only when you use them.

Example prompts

  • "Search my snippets for the retry-with-backoff helper and paste it here."
  • "Save this function as a snippet in the Work workspace, folder Utilities, tagged postgres."
  • "List my Swift snippets tagged networking."

Privacy Policy

Full policy: https://snipperapp.com/privacy

What the server collects. Nothing. snipper-mcp has no analytics, no telemetry and no crash reporting of its own. The MCPB launcher in this repository makes no network requests at all — it either hands stdio to the bundled binary or answers tools/list from a static file.

How your data is used and stored. The server reads and writes the same local SQLite database as SnipperApp 3, inside the app's own container on your Mac. Snippets, folders, tags and attachments never leave your machine unless you have turned on a sync storage yourself: iCloud (Apple CloudKit, your private database — the developer cannot read it) or GitHub Gist (your own account, under your GitHub credentials).

Third-party sharing. None by the server. The three Hub tools (search_hub, get_hub_snippet, import_from_hub) call the public SnipperApp Hub API, and only when an assistant invokes them; they send the search terms or snippet ID and nothing from your library. No snippet content is uploaded. Nothing is sold or shared with advertisers or data brokers.

Data retention. Your snippets live on your Mac and stay until you delete them; deleting them in SnipperApp 3 (or via delete_snippet) removes them from the local database and from any sync storage you enabled. There is no server-side copy for the developer to retain. Hub requests are not tied to an account and are not retained as a per-user history.

Contact. [email protected] — for questions, or to ask what is held about you and have it deleted.

This repository

  • mcpb/ — the MCPB extension: manifest.json, icon.png, and the launcher server/index.js. Rebuild with npx @anthropic-ai/mcpb pack mcpb snipperapp-<version>.mcpb.
  • server.json — the entry for the official MCP registry (mcp-publisher publish).
  • The launcher and these docs are MIT licensed; SnipperApp 3 and its bundled snipper-mcp binary are proprietary.

Support

[email protected] — bug reports, feature requests and privacy questions. Documentation: https://snipperapp.com/docs/mcp-integration

Source: README.md at commit 2e875b5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts