Bring your tool connections with the session#
MCP connections let an agent use tools supplied by other services or local servers. When continuing a session in the cloud, Ondago reviews discovered MCP configuration and prepares supported connections for the destination.
Connection review is a preview. After launch, the cloud checks initialization and tool discovery; a successful source-side review does not prove the connection will work in the cloud. A failed MCP connection does not by itself stop the agent session.
Review connections before continuing#
- On the source computer, choose Continue in cloud for the session and open its configuration or connection review.
- Inspect each discovered MCP server. Check its configuration, enabled state, and proposed destination.
- For an unapproved project connection, choose Allow this connection only after reviewing it. Existing disabled choices remain disabled.
- Choose cloud setup or Use this computer where offered. Supply the requested credentials or complete browser sign-in for the selected connection.
- Review any build-script choice, refresh the preview as needed, then complete the session’s continuation.
Only locally discoverable MCP configuration can be carried this way. A connector stored solely inside an agent vendor’s account may not appear. Signing in to an MCP server through this review does not copy the vendor’s own login session.
Choose where a connection runs#
| Connection | Cloud option | What to check |
|---|---|---|
| Local Node package | Package and install a supported server with an npm lockfile. | Dependency and file compatibility. Node build or lifecycle scripts need an explicit per-connection choice. |
| Local Python server | Prepare a supported script with requirements.txt, or pyproject.toml and uv.lock. | Dependencies must be installable in the cloud. Python installation may execute package build hooks. |
| Public package recipe | Run supported npx, uvx, or uv tool run recipes. | Pin package versions for repeatable setup; unpinned recipes resolve when setup runs. |
| Remote HTTP or SSE server | Connect directly from the cloud with scoped credentials or supported browser sign-in. | The endpoint must be reachable and its authentication supported. |
| Server that needs your computer | Choose Use this computer to relay the selected connection. | Keep the source awake, online, and able to run its original server command. |
Use this computer is useful for local services, private registries, unsupported executables, or files that cannot be packaged. The agent runs in the cloud, but that MCP server still runs on the source computer over an encrypted connection. Its access grant is limited to the selected servers and cloud run and expires after 24 hours.
Cloud packaging excludes dependencies, caches, hidden files, and credential files. Unsupported local dependencies, binary resources, symlinks, or detected secrets can prevent packaging. Follow the review’s explanation rather than assuming every local server can move.
Supply credentials for the selected connection#
Enter requested environment values or HTTP headers in connection review, or use its browser sign-in action when supported. Credentials are encrypted for the destination run and scoped to the selected connection; they are not added to the reusable session bundle.
Returning a bundle or starting a new run does not automatically give that run the previous run’s credentials. Review authentication again when prompted. Some servers require a preregistered OAuth client or an unsupported sign-in flow; use a supported configuration or the computer connection when available.
Review the cloud execution boundary when deciding which tools and accounts a cloud agent should use.
Inspect cloud connection results#
Open MCP connections from the cloud session in Desktop or the Web app, including on a phone. The panel lists included connections, their setup result, and when they were checked. Use Refresh results to retrieve the latest report.
The check verifies initialization and tool discovery. It does not invoke the server’s tools, continuously monitor the connection, or guarantee that a later service operation will succeed. The agent’s existing tool permissions still apply.
Repair a connection#
- Read the connection’s explanation in MCP connections.
- For a temporary setup failure, choose Retry connection when available.
- For missing or expired credentials supported by the panel, choose Update credentials, enter the requested values, then Save and retry.
- Wait for the result. You can close the panel while the selected connection is checked.
- If setup succeeds but the agent remembers the earlier failure, reconnect that MCP server in the agent.
Retry works on the selected connection in a running, writable session and preserves the other connections. It does not change the captured server configuration. New approval, a different package or transport, choosing Use this computer, or reconnecting a browser account requires review on the source computer and a new cloud continuation.
If a runtime compatibility message blocks continuation, update the source installation and use a compatible cloud runtime. Follow the message rather than bypassing connection review. For general transfer problems, see cloud troubleshooting.