LocalCan
About
Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control.
Details
- Author
- Unknown
- Categories
- Developer Tools, Knowledge Base, Other
Jump to
Ask your AI assistant to inspect captured traffic, manage Public URLs, and publish offline Snapshots through LocalCan's MCP server.
- Inspect captured traffic— Ask your assistant to list recent HTTP exchanges withlist_trafficand view details of any exchange viaget_exchange.
- Create and manage Public URLs— Have your assistant create a tunnel withcreate_public_url, list existing ones withlist_public_urls, and pause or resume them.
- Publish offline Snapshots— Ask your assistant to publish a folder as a Snapshot withpublish_snapshotso a link stays reachable when your machine is offline.
- Protect URLs with passwords— Have your assistant password-protect a Public URL withset_passwordand check protection viaget_access_status.
- Check capture status— Ask your assistant to verify whether capture is on and how much traffic is buffered withget_status.
localcan mcpruns a Model Context Protocol server over stdio. An MCP host (Claude Code, Codex, Cursor, Claude Desktop, and others) launches it and calls LocalCan's tools to read captured traffic, manage Public URLs (tunnels), and publish Snapshots. LocalCan must be running for the tools to return data, so open the desktop app or runlocalcan start -dfirst.
The server exposes twenty tools. Reading works out of the box. The eleven tools that change things need write access, which is off by default (see the switches below). Creating or adding a Public URL needs an active license. Publishing a Snapshot and password-protecting a URL need a subscription plan, so a perpetual license is turned away even though it can still open Public URLs. Unlicensed, the gated tools return a clear activation message, while pausing, resuming, and removing existing URLs still work.
An exchange is the request LocalCan forwarded to your backend, not a byte-for-byte copy of the client's original request. SeeTrafficfor the data model.
How you connect depends on how the agent runs. Terminal agents (Claude Code, Codex) inherit your shell PATH, so a barelocalcancommand works. GUI apps (Cursor, Claude Desktop, VS Code, and others) do not load your shell PATH, so they need the absolute path to the binary, for example/Users/you/.localcan/bin/localcan. The desktop app's Settings can copy a ready-made config with the right path filled in, which is also the reliable route on Windows.
claude mcp add --scope user localcan -- localcan mcp
Flag--scope userregisters the server for every project. Drop it to register it only in the current project.
This writes the server to~/.codex/config.toml. For the Codex desktop app or IDE extension, pass the absolute path in place oflocalcan.
{ "mcpServers": { "localcan": { "command": "/Users/you/.localcan/bin/localcan", "args": ["mcp"] } } }
- Cursor:~/.cursor/mcp.json, then enable the server in Settings.
- Claude Desktop:claude_desktop_config.json(Settings, Developer, Edit Config), then quit and relaunch.
- Windsurf:~/.codeium/windsurf/mcp_config.json, then refresh the MCP panel.
VS Code (Copilot agent mode) uses aserverskey with an explicit type. Add this to.vscode/mcp.jsonin your workspace:
{ "servers": { "localcan": { "type": "stdio", "command": "/Users/you/.localcan/bin/localcan", "args": ["mcp"] } } }
You can also runcode --add-mcpwith the same server object.
Zed usescontext_serversin itssettings.json:
{ "context_servers": { "localcan": { "source": "custom", "command": "/Users/you/.localcan/bin/localcan", "args": ["mcp"] } } }
You can also add it from the Agent Panel settings.
Agent access, redaction, and write access
All three are controlled in the desktop app under Settings (the "AI Agents (MCP)" section), or from the terminal:localcan mcp enable/disablefor agent access,localcan mcp redact <on|off>for redaction,localcan mcp access <read_only|read_write>for write access, andlocalcan mcp statusto see the current state.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Extentos is a multi-vendor development platform for adding smart-glasses capabilities to existing iOS and Android apps. The simplest analogy is Stripe for smart glasses
An MCP server tailored for React Native–first development using Gluestack UI
Create and read feature flags, review experiments, generate flag types, search docs, and interact with GrowthBook's feature flagging and experimentation platform.
Understand, develop, and debug authorization policies in Oso Cloud.
Up-to-date documentation for your coding agent. Covers 1000s of public repos and sites. Built by ref.tools
Points agents to the canonical Agentry install docs for errors, product analytics, and deploy attribution.
Gives coding agents deterministic, read-only documentation handoffs with edit boundaries, ownership, and required checks before repository changes.
Deterministic JSON checks with signed evidence and x402-paid execution
Search Apple's Developer Documentation with smart search and wildcard support.
Tamper-evident action logging for AI agents: hash-chained ledger_append/ledger_verify MCP tools over one JSONL file, zero dependencies — proves the record wasn't altered in place (limits stated honestly in the docs).
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





