reeinharddd/snapmcp

Terminal · Code · Browser · Markdown · Diff · HTML · PDF · GIF
For documentation workflows — when structured snapshots aren't enough.
---
Real terminal colors, Shiki-highlighted code, visual diffs, PDFs and GIFs — one MCP server, 13 tools. Renders with your system Chrome, or auto-installs Chromium at first setup. SSRF protection on by default. Built for agents that write documentation, not just drive browsers.
Quick Start
Three steps, under two minutes:
**1. Install**
**2. Add to Claude Code** (~/.claude/claude.json)
**3. Capture**
Ask your agent in natural language:
> "Capture a terminal screenshot of git log --oneline -5 and a syntax-highlighted PNG of src/index.ts."
The agent calls capture_terminal and capture_file — images land in ./captures/ with your real terminal theme and the chosen syntax theme applied.
Other clients: OpenCode, VS Code / Cline, Docker
**OpenCode** (opencode.json):
**VS Code / Cline / Roo-Cline** (settings.json → cline.mcpServers):
**Docker**:
What it looks like
| Capture | Preview |
|---------|---------|
| Terminal (real detected colors) | |
| Code (Shiki syntax) | |
| Diff (green/red) | |
Why snapmcp vs Playwright MCP
Different tools for different jobs. Playwright MCP drives a browser through token-efficient accessibility snapshots; snapmcp renders pixel-faithful images for humans to read. If your agent needs to *click*, use Playwright. If it needs to *show*, use snapmcp.
| Use case | snapmcp | Playwright MCP |
|----------|:-------:|:--------------:|
| Terminal capture with real colors | ✅ auto-detects Kitty, Gnome, Alacritty, WezTerm themes | ❌ no terminal support |
| Code → syntax-highlighted image | ✅ Shiki, 50+ languages, 27 themes | ❌ not its purpose |
| Git diff → visual red/green image | ✅ capture_diff | ❌ |
| URL → PDF document | ✅ capture_pdf | ❌ |
| Animated GIF from captures | ✅ capture_gif (zero-dep gifenc) | ❌ |
| Markdown → styled document | ✅ capture_markdown, capture_document | ❌ |
| Browser page screenshot | ✅ capture_browser (full-page or viewport) | ✅ |
| Browser **automation** (click, fill, navigate) | ❌ screenshots only | ✅ accessibility-tree driven, token-efficient — the right tool for this |
Most documentation pipelines pair them: Playwright MCP to *interact*, snapmcp to *document*.
Tools
| Tool | Description |
|------|-------------|
| capture_terminal | Terminal output with syntax-colored prompts (auto-detects real terminal theme) |
| capture_code | Syntax-highlighted code via Shiki (50+ languages, 27 themes) |
| capture_browser | Full-page or viewport screenshots (uses system Chrome profile when available) |
| capture_file | File → auto-detected language → highlighted screenshot |
| capture_markdown | Rendered markdown as a styled document |
| capture_html | Arbitrary HTML snippet rendered as image |
| capture_diff | Git diffs with green additions / red deletions |
| capture_pdf | URL → PDF document |
| capture_batch | Batch capture multiple items in one call |
| capture_gif | Animated GIF from multiple screenshots |
| capture_sequence | Side-by-side animated sequence |
| capture_document | Create document (MD/HTML/PDF) with embedded captures |
| snapmcp-hint | Server capability hints for MCP clients |
Use cases
**Automated documentation** — an agent writes a setup guide and embeds real captures: the terminal output of the install command (with your actual theme), the config file syntax-highlighted, the diff of the migration. One prompt, three capture_* calls, images saved next to the markdown.