How do I verify Montage workspace access with Devin Local?
Devin Local brings external tools into the agent running in Devin Desktop. The former Windsurf MCP documentation now redirects to Devin Local customizations, so this guide follows that current product rather than promising old Cascade settings still apply. Montage should enter a deliberately scoped desktop session, separate from code-editing permissions, with an authorized status response as the connection milestone.
Using Devin Local, call only Montage signals_status as the first live operation. Report the actual workspace identity and coverage from the tool response. If authentication, transport, or the tool is unavailable, stop and explain the blocker. Do not start collection, recurring tracking, writes, publishing, messaging, or social actions.Choose the current desktop surface
Open Customize in the Agents window and inspect the MCPs tab. Confirm that you are configuring Devin Local, not a cloud session or a legacy Windsurf installation. The current documentation says Local shares the Devin CLI customization format and discovery; that is a configuration relationship, not evidence that every historical client has the same remote authentication behavior.
Resolve personal versus project configuration
Review the MCP servers already loaded for the project before adding Montage. Devin supports per-project and per-user customizations, which have different sharing consequences. Prefer personal configuration when the connection is tied to your own workspace. Keep secrets out of repository settings, and distinguish an organization's supplied server definition from an authorization granted by your own Montage account.
Register the hosted server
Use the current MCP server installation and configuration controls linked from Customize to register https://app.montages.co/mcp as a remote endpoint. Do not translate a legacy local launcher example into an invented Montage executable. Inspect the effective configuration after registration, especially if imported settings already contain another Montage entry; the service address must not be duplicated under misleading names.
Keep permission and reauthentication separate
Review the documented MCP Permissions and Re-authentication sections for your installed desktop release. Complete only a supported authorization flow for the intended account. If the client cannot satisfy Montage's authentication requirements, leave the connection blocked rather than turning off permission checks. A server appearing in the MCPs tab establishes discovery, not account-scoped access or permission to change social relationships.
Test a single bounded operation
Ask Devin Local to execute only signals_status on Montage and retain the actual returned workspace identity. Do not include repository edits, recurring tasks, collection, or social actions in this first request. If it fails, distinguish a remote transport error from an expired grant before retrying. A successful result authorizes neither broader tools nor the next coding task automatically.
Keep the boundaries clear.
- The former Windsurf MCP URL now resolves to Devin Local documentation; this guide targets the current desktop client, not legacy Cascade.
- Documented setup, not live interoperability certification. A visible tool catalog is not workspace authorization.
- First live operation: read-only signals_status. No automatic collection, recurring tracking, or social actions; broader actions need separate explicit authorization.
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-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.