Skip to content

Montage for Continue

Load Montage in Continue's Agent-mode MCP configuration, resolve version-specific authorization, and check workspace access without writes.

Integrations

Why might a configured Montage server be unavailable in Continue?

Continue exposes MCP tools in Agent mode. Adding a server definition does not make those tools available in every chat mode, and a remote URL is not a login. Its .continue/mcpServers/ directory can load JSON or YAML definitions; select the format and scope already used by your project. The setup here documents a hosted Streamable HTTP connection without substituting local stdio examples.

01 / CONFIGUREOne remote endpointUse this client's documented HTTP setup
02 / AUTHORIZEYour workspace accessUse a supported sign-in or credential flow
03 / VERIFYRun signals_statusCheck a real workspace response
Continue · remote endpoint for a streamable-http definition
https://app.montages.co/mcp
Agent-mode verification request
In Agent mode, call Montage signals_status only. Report the actual workspace response or the blocking configuration/authentication error.
01 / Integrations

Begin in Agent mode

Confirm that the Continue interaction intended to use Montage is running in Agent mode. A normal chat experience without MCP tools can look like a broken connection even when a definition exists. Inspect the current project and user configuration locations so that you know which agent setup will receive the server, rather than editing an unrelated profile.

02 / Integrations

Load a remote server definition

Use the documented .continue/mcpServers/ loading mechanism for JSON or YAML, following the enclosing schema of your installed release. Select the remote type streamable-http and the Montage URL below. Do not copy a command-and-arguments stdio example: the hosted service is already running and needs an HTTP connection, not a local process launcher.

03 / Integrations

Configure authentication deliberately

Review Continue's authentication options for your installed version and apply a supported authorization method before calling account-scoped tools. Merely adding the URL cannot establish identity. Keep any approved credential outside committed server definitions and conversations. If that version cannot complete the required authorization, choose a proven OAuth client instead of presenting an unauthenticated definition as ready.

04 / Integrations

Check the Agent tool selection

Refresh the active configuration through Continue's normal controls and inspect which tools the Agent can actually use. Limit the first task to status and leave write tools unapproved. Distinguish an inactive mode, a rejected configuration and an unauthorized server response; they require different fixes and should not all be treated as a reason to change credentials.

05 / Integrations

Request signals_status and stop on failure

Have the Agent call Montage signals_status and inspect the returned workspace and source coverage. If no tool is available, recheck Agent mode and definition loading. If the server rejects authorization, repair the version-supported auth path or move to an approved OAuth client. If transport fails, confirm streamable-http and the HTTPS endpoint. Do not launch research until the authorized read-only response succeeds.

Keep the boundaries clear.

  • MCP tool use is limited to Continue Agent mode.
  • Authentication configuration is version-dependent; the endpoint alone does not sign in.
  • This is documented remote setup, not a claim of automatic OAuth parity or live certification.

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.

Know what social media shows about you.
Start with a question.

Get started
montage