--allow Expose only the tools they need
Only named tools appear in their tools/list. Calls to write_file or anything else are blocked at the gate.
Share your local MCP server
with a teammate’s agent.
Give them access to your tools over an encrypted, peer-to-peer connection. Your MCP server runs locally, and your teammate connects through MCPWire.
npx -y @mcpwire/cli Node.js 18+ Noise-encrypted P2P No account required
Works with every MCP client
Claude Code
Cursor
Codex
Windsurf
OpenCode
Kilo Code
VS Code
GitHub Copilot
Gemini CLI
Zed
Raycast
01 · On your machine
Wrap your local MCP server
Run mcpwire share in front of any stdio server. The process runs on your machine, and the CLI prints a wire:// session ticket. Keep it private: it can be reused while the session is running.
Local MCP process Credentials configured locally
Terminal · Host
npx -y @mcpwire/cli share \
--allow read_file,list_directory \
--redact-secrets --ttl 30m \
-- npx -y \
@modelcontextprotocol/server-filesystem .Session policyAll three controls apply
--redact-secrets Scrub secrets before they leave
Recognized secret patterns in outbound responses are replaced with [REDACTED_BY_MCPWIRE] locally. Detection can miss unfamiliar formats.
--ttl 30m Set a hard time or call limit
The session closes when its configured time or --max-calls budget runs out. End it sooner with Ctrl+C.
02 · On their machine
Connect their agent in one paste
Your teammate pastes the printed config into their MCP client. Once connected, their agent can call your allowed tools without installing your MCP server or configuring its API keys.
Teammate’s agent Works with any stdio MCP client
MCP client config · Teammate{
"mcpServers": {
"teleported-filesystem": {
"command": "npx",
"args": [
"-y", "@mcpwire/cli", "join",
"wire://<ticket-from-host>"
]
}
}
}Works with any
stdio MCP server
Wrap the databases, browsers, and internal tools you already run locally—no SDK changes required.
Browse all 26 server guides
FAQ
Common questions
How the tunnel, firewall, and local execution work under the hood.
Why not just share an API key or use ngrok / SSH?
An API key grants access within that key’s permissions. MCPWire adds MCP-aware tool filtering, response redaction, and session limits to the connection, while your server’s credentials remain configured on your machine. These controls would need to be added around a generic network tunnel.
Does my teammate need to install the MCP server or its dependencies?
No. Your teammate only needs Node.js 18+ so their client can run npx -y @mcpwire/cli join wire://.... Even if your MCP server requires Python, Docker, local databases, or internal VPN access, all of that stays and executes on your machine.
How does peer-to-peer connection work behind NAT and firewalls?
MCPWire uses the public Hyperswarm DHT for peer discovery and UDP hole-punching to attempt a Noise-encrypted peer connection. The wire:// ticket identifies the session’s discovery topic; the Noise handshake establishes encryption. Restrictive NATs or firewalls can prevent a connection. MCPWire does not operate its own relay service or guarantee connectivity on every network.
Can I approve each tool call manually or audit what their agent did?
Yes. Add --confirm to approve tool calls in your terminal. You can allow or deny a call, or approve that tool for the rest of the session. Add --record session.wirelog to save a local audit trail for the session replay viewer.
What secrets does --redact-secrets catch?
With --redact-secrets enabled, MCPWire scans outbound response payloads for recognized API keys, bearer tokens, JWTs, PEM private keys, email addresses, and card numbers. Matches are replaced with [REDACTED_BY_MCPWIRE]. Detection is pattern-based and can miss unfamiliar formats.
Connect your own tools
Server setup, access policies, and the full CLI flag reference.