Skip to content

Montage for Claude Code

Connect Montage's social media research MCP server to Claude Code. Follow the setup command, authorize your workspace and verify search and watchlist tools.

Integrations

What does connecting Claude Code actually do?

Connect your existing agent to the same private workspace you use in the Montage app. The remote server handles research and workspace tools; your client handles its own conversation and authentication controls. Start with the setup specific to your client, then prove access with a real, read-only tool response.

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 · terminal
claude mcp add --transport http montage https://app.montages.co/mcp
Claude Code · authenticate if requested
/mcp
First prompt
Use Montage signals_status. Tell me which workspace is connected and what source coverage is available.
01 / Integrations

Add the HTTP server in Claude Code

Run the add command from your terminal where Claude Code is installed. This registers Montage in your client configuration; it does not sign you in or prove that a workspace tool can run. Use the appropriate project or user scope in Claude Code for the machines and repositories where you want the server available.

02 / Integrations

Authenticate when Claude Code asks

Open /mcp, select Montage and use its authentication action if the client requests it. Your browser opens Montage. If you are already signed in, review the agent and requested permissions; otherwise use an available Google or GitHub sign-in first. Return to Claude Code after approving. No Montage API key needs to be pasted into a conversation.

03 / Integrations

Verify a real workspace response

Ask for signals_status before doing collection work. Check that the workspace and available sources are the ones you expected. A metadata response, copied command or tool list is not the same as an authorized workspace response. If authorization is expired or revoked, authenticate again rather than replacing the endpoint or using an unrelated account.

Keep the boundaries clear.

  • No API key to copy for normal OAuth-capable clients.
  • The agent uses your workspace’s plan, limits and research credit.
  • Client support and UI labels vary; do not promise an app-store integration.

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