Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Local snapWONDERS MCP: hide, reveal, analyse and convert files on your own machine
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SNAPWONDERS_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
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": {
"local": {
"command": "uvx",
"args": [
"snapwonders-mcp"
],
"env": {
"SNAPWONDERS_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add local --env SNAPWONDERS_API_KEY=your-value -- uvx snapwonders-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"local": {
"command": "uvx",
"args": [
"snapwonders-mcp"
],
"env": {
"SNAPWONDERS_API_KEY": "your-value"
}
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"local": {
"type": "stdio",
"command": "uvx",
"args": [
"snapwonders-mcp"
],
"env": {
"SNAPWONDERS_API_KEY": "your-value"
}
}
}
}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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 9, 2026
The registry name was verified against the domain snapwonders.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: SNAPWONDERS_API_KEY
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).
The GitHub repo last changed –, and the latest version (0.1.4) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
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.
snapWONDERS — Expose what's hidden. Hide what's yours.
A local MCP server that lets an AI assistant work on files on your own machine — hide a file inside a photo, reveal hidden content, run forensic analysis, or convert between formats.
Claude Desktop ──stdio──▶ snapwonders-mcp ──HTTPS──▶ snapwonders.com/api
(your machine) (your machine)
snapWONDERS already has a remote MCP server at https://snapwonders.com/mcp, and for orchestration it works well. But it runs on *our* servers — so it cannot see your files, and MCP tool calls carry JSON rather than bytes. An assistant with a photo on your desktop could create a session and then have nowhere to put the file.
This server runs where your files are. You give it a path, it reads the file locally and uploads it over HTTPS alongside the conversation. That is the whole difference, and it is what makes snapWONDERS usable from Claude Desktop, which has no terminal for an assistant to fall back on.
Results come back the same way: a hide, reveal or convert writes the output to your disk and tells the assistant where it landed — not an asset id you would need a separate HTTP client to redeem.
You need an API key from https://snapwonders.com/profile/api-keys (free account, and the address must be verified — an unverified account's keys are always rejected).
Nothing to install ahead of time if your client can run uvx:
uvx snapwonders-mcp
Or install it properly:
pip install snapwonders-mcp
%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS:
{
"mcpServers": { "snapwonders": { "command": "uvx", "args": ["snapwonders-mcp"], "env": { "SNAPWONDERS_API_KEY": "sw_your_key_here" } } } }
claude mcp add snapwonders --env SNAPWONDERS_API_KEY=sw_your_key_here -- uvx snapwonders-mcp
~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
"mcpServers": { "snapwonders": { "command": "uvx", "args": ["snapwonders-mcp"], "env": { "SNAPWONDERS_API_KEY": "sw_your_key_here" } } } }
The key is read from the environment, never taken as a tool argument — so it does not pass through the model's context, where it would end up in transcripts and logs.
Passwords are different, and you should know it. hide_file and reveal_file take the passphrase *as a tool argument*, because only the user can supply it and it changes per call. That means it does pass through the model's context and may appear in client logs and transcripts. There is no way around that in an assistant-driven flow — but the care taken with the API key does not extend to the passphrase, so treat anything you hide through an assistant accordingly.
This server can upload any file you can read. That is the point of it — an assistant asks for a path and the file is sent to snapWONDERS for processing. It also means a request like "analyse ~/.ssh/id_rsa" would do exactly that, and an assistant following instructions from a web page or document it has read could try to use it that way. Your MCP client's tool-approval prompt is the real gate: read the path in the tool call before approving it.
| Tool | What it does |
|---|---|
analyse_file | Forensic analysis of a local image or video — A–F grade, metadata exposure, manipulation evidence, hidden content. Optional face detection and OCR. |
hide_file | Conceal a file inside a cover image or video, and save the result to disk. |
reveal_file | Extract content hidden in an image or video, and save it to disk. |
convert_file | Convert an image or video to another format, and save the output to disk. |
Four tools, each a whole task. The REST API underneath is a session → upload → job → poll → results sequence; exposed one call per step, a model has to carry five-step state and will sometimes get it wrong. The orchestration lives here in Python instead, where it is deterministic.
Passwords for `hide_file` are not recoverable. They are never stored, and there is no
reset. Be sure the user knows the passphrase before hiding something with it.
https://snapwonders.com/mcp needs no install and is right when the files are already somewhere the server can reach, or when you only want session and job orchestration. Use this local server when the files are on the user's machine — which, for a desktop assistant, is almost always.
Whichever fits, and you never choose: the Python SDK sends anything under the server-reported cap (currently 95 MB) as a single direct upload, and falls back to the resumable TUS protocol above it.
This project started with my son, Huey.
Huey lost his eyesight and was legally blind from the age of four. Years ago, in the car, while we were working on Hueyify together, he insisted the idea could be applied to digital media: stories embedded inside a photo, so that people with vision impairments could get the personal context, the memory and the feeling behind it. Hidden from everyone else. Only for the person it was meant for.
He was excited at the thought of it. I'll admit the technical difficulty put me off, and I was vocal about it. The look of disappointment kept returning to me, because to Huey it all made sense. We lost Huey at sixteen. I could never let go of that conversation.
snapWONDERS came first, to understand what digital media actually contains and who can see it. Vaultify came after, and it is the closest thing I've built to what Huey described. As of September 2026, snapWONDERS and Vaultify have processed more than six million media jobs.
The full story is at https://vaultify.snapwonders.com/our-story
May peace be with you,
Kenneth Springer
MIT — see LICENSE. The licence covers this server only; the snapWONDERS API it calls is proprietary.