Connect Copilot Chat in local VS Code
ExperimentalThis integration has not passed a RateLoop release smoke test at a pinned client version.
Uses a top-level servers object, not mcpServers. No RateLoop OAuth client ID or redirect URI is preregistered or guessed; distinct from GitHub's cloud agent, which lacks remote OAuth MCP.
What to expect
- Add the server entry to the local mcp.json and start it
- Use the host's Auth action when it appears
- 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
Local mcp.json servers entry; leave the optional oauth.clientId unset — none is preregistered
{
"servers": {
"rateloop-workspace": {
"type": "http",
"url": "https://www.rateloop.ai/api/agent/v1/mcp"
}
}
}Checked 2026-07-17 against provider-docs-snapshot@2026-07-17.
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.