What must I check before calling Montage tools from Roo Code?
Roo Code documents remote Streamable HTTP MCP connections, but transport support alone does not prove compatibility with a server's OAuth flow. Use this guide to separate configuration precedence, remote discovery and authorized execution. The project-level .roo/mcp.json can override global mcp_settings.json, making effective configuration an important first diagnostic rather than a detail to discover after repeated sign-in attempts.
https://app.montages.co/mcpExecute Montage signals_status only if authorization is configured. Report its real workspace result or stop with the authentication error.Resolve project and global precedence
Inspect the project's .roo/mcp.json and the applicable global mcp_settings.json before registering Montage. Identify any existing montage key and determine which file wins for the active project. Preserve unrelated server entries. A correct global URL can appear ineffective when a project override still points elsewhere, so resolve that conflict before investigating authentication.
Select the documented remote transport
Use Roo Code's documented Streamable HTTP server configuration under mcpServers for your installed release. Set the remote address to the endpoint below rather than a local executable or SSE example copied from another server. The endpoint snippet intentionally avoids imposing transport property spelling from a different client or an incompatible Roo version.
Establish an actually supported auth path
Verify that the installed Roo version supports Montage's OAuth requirements before claiming a connection. If it does not, an existing approved Team credential may be configured securely by its owner where supported. This guide creates no credential and includes no secret template. Otherwise choose a documented OAuth-capable client instead of attempting to bypass authorization.
Inspect tools without widening permission
Once the authorized transport initializes, inspect the server's tool definitions and choose the status tool explicitly. Keep approval decisions separate from connection troubleshooting. Do not turn on broad automatic execution to make a warning disappear, and do not regard a visible list of tools as evidence that every operation is allowed for this account.
Close setup with signals_status
Request a real authorized Montage signals_status response and compare its workspace with the intended account. If authorization is unavailable, stop and report the missing client capability; if transport fails, revisit the effective project override and Streamable HTTP settings. A different approved OAuth client is a valid fallback, but no failed Roo attempt should be presented as a successful connection.
Keep the boundaries clear.
- Roo OAuth compatibility with Montage has not been live-tested by this guide.
- Project .roo/mcp.json overrides can change the server used despite correct global settings.
- Without compatible OAuth or an owner-supplied approved Team credential, use a documented OAuth client.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.