// teleport guide · Observability · official

Teleport Sentry MCP — read-only, P2P, zero cloud

Sentry's MCP server is designed around read-heavy issue triage, which makes it an ideal teleport target: a teammate helping you debug gets stack traces and tags through the tunnel, and the DLP shield scrubs tokens that appear in event payloads. This guide maps all 8 tools of @sentry/mcp-server by blast radius, then gives you the exact command to share it with a remote teammate's AI agent — capability without credentials.

4SAFE to expose

2CAUTION

2KEEP LOCAL

0servers involved

host terminal — read-only share command

npx -y mcpwire share --allow "search_issues,get_issue_details,list_organizations,list_projects" --redact-secrets --ttl 30m -- npx -y @sentry/mcp-server

Only the 4 read-only tools are exposed; the other 4 are invisible to the peer (filtered from tools/list and blocked if forced). Tunnel dies in 30 minutes. Add --confirm to approve every call, or --max-calls 20 for a hard budget.

peer config — claude_desktop_config.json / .cursor/mcp.json

{
  "mcpServers": {
    "teleported-sentry": {
      "command": "npx",
      "args": [
        "-y",
        "mcpwire",
        "join",
        "wire://<TICKET_FROM_HOST_BANNER>"
      ]
    }
  }
}

🛡️ tool risk map — Sentry

tool	risk	notes
`search_issues`	SAFE	Issue search.
`get_issue_details`	SAFE	Issue metadata + counts.
`get_issue_events`	CAUTION	Raw events may embed PII/headers.
`get_trace_details`	CAUTION	Distributed trace spans.
`list_organizations`	SAFE	Org index.
`list_projects`	SAFE	Project index.
`create_issue_comment`	HIGH RISK	Posts comments.
`update_issue_status`	HIGH RISK	Resolves/reopens issues.

🔒 Why not just share your token?

Sentry's credential would grant the full toolset to a foreign LLM — including create_issue_comment and update_issue_status. With mcpwire the credential stays in your env; the peer only ever holds an expiring wire:// capability scoped to 4 tools.

🎥 Audit everything

Add --record session.wirelog and every call, block and redaction is logged locally. Drag the file into mcpwire.co/replay for a DevTools-style waterfall of what the remote agent actually did.

🔁 Works with every MCP client

Claude Desktop, Cursor, Windsurf, Cline — anything speaking MCP over stdio. Your peer pastes the snippet above; you keep the kill-switch (Ctrl+C) in your terminal.

What happens if the peer's agent tries to call a blocked Sentry tool?

The request never reaches your MCP server. mcpwire answers with a JSON-RPC error (-32601 [MCPWire Firewall]) and logs the attempt — the tool doesn't exist from the agent's point of view, so well-behaved agents won't even try.

Can I expose the caution-level tools too?

Yes — just add them to --allow or run with --confirm so each call waits for your y/n in the host terminal. The risk map above tells you exactly what you'd be signing up for.

Is the traffic really serverless?

Yes. Discovery goes through the public Hyperswarm DHT; the data path is a direct Noise-encrypted socket between the two machines (UDP hole punching). If both NATs are stubborn, Hyperswarm routes through community relays — which only see ciphertext.

← all teleport guides ⚡ open the policy builder

🔒 MCPWire Enterprise & Team Mesh (Early Access)

Need persistent wire://your-company/db namespaces, SSO / GitHub identity verification before the P2P handshake, and centralized audit logs for compliance (SOC2 / ISO)?