Skip to content

Montage for Anthropic MCP connector

Anthropic's MCP connector lets the Messages API reach remote MCP servers without a separate application-side MCP client.

Integrations

How do I verify Montage workspace access with Anthropic MCP connector?

Anthropic's MCP connector lets the Messages API reach remote MCP servers without a separate application-side MCP client. The documented request combines mcp_servers with a matching mcp_toolset entry. This path is distinct from Claude Desktop and Claude Code, and its beta version, supported transports, and data-handling limitations must be checked before sending workspace information through a hosted API request.

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
Anthropic MCP connector · read-only verification prompt
Using Anthropic MCP connector, call only Montage signals_status as the first live operation. Report the actual workspace identity and coverage from the tool response. If authentication, transport, or the tool is unavailable, stop and explain the blocker. Do not start collection, recurring tracking, writes, publishing, messaging, or social actions.
01 / Integrations

Review the connector’s current limitations

Read the Messages API section rather than assuming Managed Agents uses the same request shape. The connector supports tool calls through publicly exposed HTTP servers, including Streamable HTTP and SSE, not direct local stdio. Its documentation currently marks this path not ZDR eligible and not HIPAA eligible; do not transfer an application's stronger privacy claim to this feature.

02 / Integrations

Pair the server and toolset definitions

Give the Montage server a unique name, type url, and address https://app.montages.co/mcp in mcp_servers. Reference that name from exactly one mcp_toolset in tools. Match the beta header to the documented connector version; the older mcp-client-2025-04-04 path is deprecated. Avoid combining old tool configuration fields with the newer toolset structure.

03 / Integrations

Manage authorization outside the request text

Supply an already authorized OAuth Bearer token through authorization_token using secure application configuration. The connector consumes the token; it does not establish that your application has implemented consent and refresh. Never place the credential in messages or logs. Without an approved Montage grant, do not make a paid request hoping discovery will sign in automatically.

04 / Integrations

Default-deny the initial toolset

Use the documented toolset defaults and per-tool configuration to enable only the actual signals_status tool during verification. Inspect its published schema before choosing arguments. A tool catalog returned through the connector does not prove workspace authorization or permit all future requests. Keep the server name unambiguous when several remote services are present.

05 / Integrations

Validate the returned tool result

Make the first live Montage operation signals_status and examine the remote result, not only the assistant's concluding prose. Verify the intended workspace and preserve authorization failures. This guide sends no paid model call and claims no live certification. Broader research, collection, recurring tracking, and social actions remain outside the initial connector test and require separate explicit authorization.

Keep the boundaries clear.

  • Messages API MCP connector is beta, tools-only, publicly reachable HTTP, and currently not ZDR or HIPAA eligible; Managed Agents is a separate path.
  • Documented setup, not live interoperability certification. A visible tool catalog is not workspace authorization.
  • First live operation: read-only signals_status. No automatic collection, recurring tracking, or social actions; broader actions need separate explicit authorization.

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-15. 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