Skip to content

Montage for Dify

Dify imports external MCP tools through its workspace Integrations area, while publishing a Dify app as an MCP server is a separate workflow.

Integrations

How do I verify Montage workspace access with Dify?

Dify imports external MCP tools through its workspace Integrations area, while publishing a Dify app as an MCP server is a separate workflow. Current documentation supports HTTP servers and explains identifier-based tool references across apps and exported workspaces. For Montage, choose a stable identifier and establish authorization before attaching tools to an Agent node; changing that identifier later can break existing applications.

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
Dify · read-only verification prompt
Using Dify, 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

Open workspace tool management

Go to Integrations, Tools in the Dify workspace that owns the application. Choose MCP rather than Swagger API or Workflow tooling. Confirm who can manage workspace-level connections, since a maker's ability to edit an app does not necessarily include authority to approve an external service. Inspect existing server identifiers before adding another entry that could be confused with an established Montage connection.

02 / Integrations

Register a stable HTTP server identifier

Provide the hosted URL https://app.montages.co/mcp, a recognizable display name, and a unique server identifier. Dify supports HTTP MCP servers in this workflow, not a local stdio command. Keep the identifier stable: apps and exports reference it, and recreating an app in another workspace requires matching server setup there. A matching identifier alone does not carry credentials or consent between workspaces.

03 / Integrations

Review dynamic client registration

Dify enables Dynamic Client Registration by default for OAuth and documents manual client credentials when automatic registration is unavailable. Leave registration on when supported; do not invent a client ID or secret. A manual OAuth application is a separate authorization prerequisite, not a step this guide completes. Keep any existing approved header credential inside secure configuration and never copy it into app prompts or exported examples.

04 / Integrations

Attach only the intended imported tool

After authorization and import, select the status tool in the test application's tool configuration. Updating the imported tool list can break an app when a schema disappears or changes, so review changes before applying them broadly. A visible imported catalog does not prove that the signed-in Montage account has workspace permission. Avoid adding a whole research sequence to an Agent node during connection testing.

05 / Integrations

Check one response before app publication

Request signals_status as the first live Montage operation in a controlled test run. Read the actual returned workspace and coverage, and preserve an authorization error as a blocker rather than an empty result. Do not publish the app or export it with secret-bearing settings as part of this check. Successful status establishes a bounded connection, not permission for automatic collection, recurring tracking, or social actions.

Keep the boundaries clear.

  • The cited current page covers Cloud workspace MCP tools; self-hosted deployments must match their own release documentation.
  • 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