Feature request: MCP server quickstart template for local desktop app integration

Problem

Two gaps that block local desktop apps from integrating cleanly with Claude:

1. Claude API blocks direct browser requests (CORS)
Browsers cannot call api.anthropic.com directly — Anthropic returns a CORS block.
This forces every local app developer to build a custom localhost proxy just to use the Claude API from a browser-based app. There is no official workaround documented for this use case.

Workaround required today: proxy server at localhost that forwards requests server-side (e.g. urllib.request in Python, fetch in Node) — not obvious for beginners, undocumented.

2. No MCP quickstart for local browser app + Claude Code integration
MCP (Model Context Protocol) is powerful for letting Claude call local tools, but there is no example or template for the most common local-AI-app pattern: a browser-based desktop app (served from localhost) that wants to register itself as an MCP server so Claude Code can read its live state, push fixes, and restart services.

Requested

1. Official docs or example: "How to use Claude API from a browser/local app" (CORS proxy pattern)
2. MCP quickstart template: minimal Python or Node MCP server for a local desktop app, with get_app_state, read_file, push_fix, restart_service tool examples
3. Ideally: claude mcp add --local command that scaffolds the boilerplate

Context

Building a local-first homestead/ham radio app (offline-capable, Ollama + Claude backends). The CORS issue and MCP integration gap are the two biggest friction points for local AI app developers. This affects anyone building Electron, Tauri, or localhost-served browser apps with Claude integration.