Skip to content

Troubleshoot Montage MCP sign-in

Recover from an unauthenticated MCP connection using the client-specific OAuth flow, then verify a real read-only workspace response.

Guides

The server is listed, but can your agent access the workspace?

Adding a server entry or seeing a tool catalog does not prove authorized workspace access. A client may still need authentication, renewed consent or a plan that supports custom remote servers. Diagnose the exact stage before changing configuration, and keep account credentials and tokens out of chat.

Read-only connection check
Run Montage signals_status and report whether this is a real authorized workspace response. If authentication is required, direct me to this client's normal sign-in action. Do not ask me to paste access tokens, cookies or secrets into chat.
01 / Guides

Check endpoint and client support

Use the signed-in remote endpoint https://app.montages.co/mcp, not the separate synthetic demo. Follow the setup guide for your actual client; configuration shapes and custom-connector availability differ. If an organization policy blocks remote MCP, resolve that policy with its owner rather than trying unrelated endpoints or bypassing the restriction.

02 / Guides

Use the client's authentication action

In Claude Code, inspect Montage through /mcp and use its authentication action when requested. Other clients expose their own connection or connector controls. Sign in to the intended Montage account and review the client name and requested workspace permissions before consenting. A browser page opening is only a step in the flow, not proof it completed.

03 / Guides

Distinguish expired access from source errors

An unauthenticated result calls for the client-supported sign-in recovery; a source_unavailable result concerns evidence availability instead. OAuth-capable clients can manage refresh tokens, but revoked or expired access can require another sign-in. Do not paste a token, browser cookie or copied account secret into the conversation to work around a failed authorization flow.

04 / Guides

Verify the real workspace

Return to the agent and request signals_status. Read the actual workspace response and available coverage before collecting data or making changes. If access still fails, retain the non-secret error and the stage that failed for support. Normal OAuth-capable usage does not require creating a Team API key merely to make the client connection work.

Keep the boundaries clear.

  • A tool catalog or opened consent page is not a successful workspace check.
  • Client plan and organization policy can restrict custom MCP availability.

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