Peepit MCP Server

Give your AI agents super-vision: blazing-fast macOS screenshots, smart window targeting, and local or cloud AI image analysis—all via a friendly Node.js MCP server. Exposed over MCP by the peepit mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Ever wish your AI assistant could just look at your screen and get it? PeepIt is here to grant your digital sidekick the gift of sight—no magic wands required. Whether you're debugging a UI, capturing a bug in the wild, or just want to know what's lurking behind that mysterious window, PeepIt's got your back (and your screen).

PeepIt is a macOS-only MCP server that lets AI agents capture screenshots of your apps, windows, or the whole system—then analyze them with local or cloud-based AI models. It's like giving your AI a pair of glasses and a magnifying glass, all in one.

• 🚀 Fast & Non-intrusive — Blink and you'll miss it—PeepIt uses Apple's ScreenCaptureKit for lightning-fast screenshots, all without hijacking your window focus or interrupting your groove
• 🎯 Smart Window Targeting — Fuzzy matching so sharp, it'll find the right window even if you only remember half its name (we've all been there)
• 🤖 AI-Powered Analysis — Ask questions about your screenshots and get answers from GPT-4o, Claude, or local models—because sometimes you need a second set of (robotic) eyes
• 🔒 Privacy-First — Prefer to keep things on the down-low? Run everything locally with Ollama, or call in the cloud cavalry only when you really need it
• 📦 Easy Installation — One-click install via Cursor, or just a quick npm/npx incantation—no arcane rituals required
• 🛠️ Developer-Friendly — Clean JSON API, TypeScript support, and logs so comprehensive you'll wonder if PeepIt is secretly writing your memoirs

Adding it to your client

incantation on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• Requirements — The Requirements tool exposed by this server
• Configuration — PeepIt is as configurable as your favorite text editor. Use environment variables to tune it to your workflow:

Configuration

You will need 8 environment variables: PEEPIT_AI_PROVIDERS, OPENAI_API_KEY, PEEPIT_LOG_LEVEL, PEEPIT_LOG_FILE, PEEPIT_DEFAULT_SAVE_PATH, PEEPIT_CONSOLE_LOGGING, PEEPIT_CLI_TIMEOUT, PEEPIT_CLI_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• macOS 14.0+ (Sonoma or later) - Node.js 20.0+ - Screen Recording Permission (don't worry, you'll be prompted—no need to go spelunking in System Settings)

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the peepit mcp server does with a few real requests.

When to reach for it

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Peepit's toolset — Requirements, Configuration — is a fair guide to whether it matches your workflow. It is maintained by MantisWare; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.