// teleport guide · Comms · official

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

The official Slack server authenticates with YOUR bot token. Teleport the listing/search tools so a teammate's agent can research threads, and put slack_post_message behind Human-in-the-Loop confirmation so nothing ships to a channel without you. This guide maps all 6 tools of @modelcontextprotocol/server-slack by blast radius, then gives you the exact command to share it with a remote teammate's AI agent — capability without credentials.

3SAFE to expose

1CAUTION

2KEEP LOCAL

0servers involved

host terminal — read-only share command

npx -y mcpwire share --allow "slack_list_channels,slack_get_channel_history,slack_search_messages" --redact-secrets --ttl 30m -- npx -y @modelcontextprotocol/server-slack

Only the 3 read-only tools are exposed; the other 3 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-slack": {
      "command": "npx",
      "args": [
        "-y",
        "mcpwire",
        "join",
        "wire://<TICKET_FROM_HOST_BANNER>"
      ]
    }
  }
}

🛡️ tool risk map — Slack

tool	risk	notes
`slack_list_channels`	SAFE	Channel index.
`slack_get_channel_history`	SAFE	Thread/message history.
`slack_get_users`	CAUTION	Member directory (PII — keep DLP on).
`slack_search_messages`	SAFE	Message search.
`slack_post_message`	HIGH RISK	Posts to channels as your bot.
`slack_reply_to_thread`	HIGH RISK	Replies as your bot.

🔒 Why not just share your token?

Slack's credential would grant the full toolset to a foreign LLM — including slack_post_message and slack_reply_to_thread. With mcpwire the credential stays in your env; the peer only ever holds an expiring wire:// capability scoped to 3 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 Slack 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)?