How should a Warp Agent reach Montage's hosted MCP endpoint?
Warp documents MCP servers in its Agents settings, including URL-based remote servers. Montage uses that hosted Streamable HTTP route rather than a shell process launched by your terminal. Authentication handling depends on the current Warp client, so treat consent support as a capability to verify, not something established by a saved URL. No browser cookies, local server launcher or private credential examples are required here.
https://app.montages.co/mcpUse Montage signals_status only. Report the real workspace response, or stop and explain the missing transport or authorization capability.Open the Agent server settings
Navigate to Settings, Agents and MCP servers in the installed Warp client, using its current documentation if labels have moved. Inspect existing entries before adding another Montage server. Confirm that you are configuring the Agent that will make the request rather than changing an unrelated shell environment or assuming every terminal session shares the same tool selection.
Add a URL-based server
Choose the Add URL server workflow and select Streamable HTTP where the interface requests a transport. Enter https://app.montages.co/mcp exactly. Do not supply a local command, a localhost proxy or a documentation page as the server address. The endpoint is already hosted, so the terminal does not need to run a Montage process.
Validate current authorization support
Follow the authentication controls documented for your Warp release and complete any supported Montage consent flow with the correct account. A saved URL without authorization is not a connection receipt. If the installed client cannot support the required flow, stop and use a documented OAuth-capable client instead of importing browser cookies or inventing a bearer token.
Separate tool availability from shell power
Inspect the Agent's discovered MCP tools and keep the first request limited to workspace status. The fact that Warp can run shell commands is not permission to create credentials or work around remote account controls. Review tool approval prompts carefully, and leave collection and workspace mutations outside this initial setup task.
End on the signals_status result
Ask the Warp Agent to call Montage signals_status and verify the actual workspace and available coverage in its response. If the tool is absent, revisit Agent server selection and transport settings; if authorization is rejected, use supported authentication controls or the OAuth-client fallback. Do not report success from a settings screenshot, and do not substitute a research operation for the read-only verification.
Keep the boundaries clear.
- Warp authentication behavior depends on the current client; automatic OAuth parity is not certified.
- Use a remote URL server, not a local Montage process or copied browser cookies.
- This documented setup does not imply native social actions or an app-store partnership.
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.