Connect Zed

ExperimentalThis integration has not passed a RateLoop release smoke test at a pinned client version.

With no Authorization header configured, the host starts the OAuth flow on first use; tool lists reload without a restart.

What to expect

1. Add the context_servers entry to the host's settings.json
2. Approve the RateLoop OAuth consent screen

Connect your workspace

Copy your message from Connections and paste it into this app. It contains a private, single-use link. Keep the complete message private.

Connect this chat to my RateLoop workspace: call RateLoop's rateloop_connect_workspace tool once with the private link below. If no RateLoop tools are available, stop and tell me to add RateLoop first. Don't open, repeat or share the link. It works once. Check each answer with RateLoop and show its review status.

/connect/aci_...#...

Host-native setup

{
  "context_servers": {
    "rateloop-workspace": {
      "url": "https://www.rateloop.ai/api/agent/v1/mcp"
    }
  }
}

Check and recover

The connection is ready only after rateloop_connect_workspace or rateloop_verify_connection verifies it. If tools are missing, check the app's server setup and policy. After access expires or is revoked, complete the app's OAuth prompt, then create a targeted reconnect message in Connections (or a new message if the agent was deleted). Never reuse a claimed link. Recovery guide.

Delivery controls remain advisory; your workflow decides when to send an output.