If the Rydoo MCP server isn't working as expected, try the fixes below.
The connection doesn't work
Restart your AI client after setting it up, and confirm you signed in to a Rydoo production account (not a sandbox or test account). If you configured the connection manually, check the server address is exactly https://mcp.rydoo.com.
Sign-in doesn't finish
Make sure your browser allows the Rydoo sign-in window to open (check for a blocked pop-up), then try again.
Rydoo isn't responding, or tools are missing
Disconnect and reconnect Rydoo in your settings.
For example in Claude, go to Settings > Connectors: then restart the app so it picks up the connection.
🆕 The Rydoo MCP server gained new capabilities in August 2026. If you connected before then, your assistant may still be showing the older set of tools. The list refreshes by itself the next time you open it. Disconnect Rydoo in your settings, connect it again, and restart the app.
A custom or third-party client won't connect
Some clients require Rydoo to approve (whitelist) their domain first.
Claude, ChatGPT and Cursor are already approved. Clients such as Windsurf, Glean and custom implementations need approval before they can connect. More details here.
You see less data than expected
The assistant can only see what your Rydoo role and permissions allow. If you think you should have more access, check your role in Rydoo.
Need help?
- Full setup, authentication, and troubleshooting details: developers.rydoo.com/page/mcp
- Found a bug, or missing something? Ask your assistant to send feedback to Rydoo. It goes straight to the team that builds the MCP server.
- Still stuck? Check your AI client's connection settings for error messages, or contact Rydoo support.