Skip to content

Connect your first agent

From a server URL to a successful workspace-tool response.

Guides

How do you know it is actually connected?

Connecting should be one server entry, a browser consent flow when needed, and a small read-only verification. You do need a Montage account for the real service, but you do not need to sign in before every tool call or manually manage a key in an OAuth-capable client. The separate no-account demo uses synthetic samples and is not a replacement for live workspace access.

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
Claude Code · add the remote server
claude mcp add --transport http montage https://app.montages.co/mcp
First prompt
Run Montage signals_status and tell me the connected workspace and available source coverage.
01 / Guides

Add the server in your own client

For Claude Code, run the command shown here. Other clients use the same HTTPS endpoint but may require a different configuration shape or a custom-connector interface. Follow the client-specific integration guide. A normal OAuth-capable agent does not need a Team API key, a local Montage worker or access to your browser session files.

02 / Guides

Sign in and review consent

When authentication is requested, your client opens Montage. Existing users can reuse a valid web sign-in; signed-out users use the enabled Google or GitHub option. Review the client name and requested workspace permissions before approving. Export is separately opt-in, and ordinary research authorization does not grant permission to follow, post or message through a social account.

03 / Guides

Verify and recover without guessing

Return to your agent and request signals_status. Its real workspace result is the connection check. If you see an authentication prompt or expired-access error, use the client’s authentication action again; supported clients manage refresh tokens between uses. If custom MCP is unavailable in your client plan or organization, resolve that requirement rather than pasting secrets into chat or trying an unrelated endpoint.

Keep the boundaries clear.

  • Examples describe the workflow, not a fabricated live dataset.
  • An MCP connection does not authorize follows, messages or posts.

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