Skip to main content
RateLoopAI Assurance Loop
← Back to Connect a Host

Connect Windsurf

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

Remote entries use serverUrl, not url; after editing the configuration, the assistant panel's refresh action reloads servers without a restart.

What to expect

  1. Add the server entry to the host's mcp_config.json
  2. Refresh the MCP server list in the assistant panel
  3. 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.

Example connection message

This example shows the instructions your agent receives. Its placeholder link cannot connect a workspace.

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

mcp_config.json entry; the remote transport field is serverUrl, not url

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

Checked 2026-08-21 against provider-docs-snapshot@2026-08-21.

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.

Connect Windsurf | RateLoop