Spectr MCP server — turn a screen recording into a production-ready spec.md, from inside Claude Code / Cursor / any MCP client.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"spectr-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# spectr-mcp MCP server that exposes [Spectr](https://spectr.to)'s spec-generation pipeline as a tool any MCP client can call. Hand it an App Store URL or a local MP4 of an app, get back a production-ready `spec.md` precise enough to build a clone from. ``` See an app. Ship an app. ``` ## What it does One tool, `generate_spec(source, ...)`: - **`source`** — an App Store URL (e.g. `https://apps.apple.com/us/app/doordash/id719972451`) or an absolute path to a local MP4 screen recording. - Returns a structured 7-section markdown spec covering app overview, navigation, screens, components, design system (with exact hex/px/weight values), implementation notes, and a Claude Code prompt the developer can paste. - Targets Expo SDK 54 / React Native / iPhone 15 baseline. Typical run: 2–5 min for App Store URLs, 5–10 min for MP4 recordings. ## Two ways to install ### Hosted (recommended) — Claude web app connector Open Claude → Settings → Connectors → Add a custom connector → paste: ``` https://mcp.spectr.to ``` No key, no install, no env vars. The hosted MCP runs on Spectr's Anthropic key; you just paste the URL and start asking Claude to generate specs. ### Local (developer install) — stdio via Claude Code If you have **Claude Code** installed and logged in (`claude login`), you can also run the MCP locally as a stdio subprocess. Uses your existing Claude Pro/Max subscription — no API key needed. ### Claude Code ```bash claude mcp add spectr -- uvx spectr-mcp ``` Or for local development against this repo: ```bash claude mcp add spectr -- uvx --from /path/to/spectr spectr-mcp ``` ### Other clients (Cursor, Codex, custom MCP hosts) Any client that supports MCP stdio servers can launch the local version: ```bash uvx spectr-mcp ``` If you don't have the `claude` CLI installed and authenticated, the MCP needs an `ANTHROPIC_API_KEY` instead — set it in the launching process's environment. Or use the **hosted** version at `https://mcp.spectr.to` if your cli…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.