Workfront Fusion MCP and Adobe Coworker integrations are now live

Overview

Today we’ve turned on the Fusion MCP server and integrated Fusion with Adobe Coworker. That means you can now interact with your Fusion organization — scenarios, executions, connections, webhooks, data stores, activity logs, and more — via natural‑language in Coworker or any MCP‑compatible agentic platform that supports remote (Streamable HTTP) MCP servers with OAuth.

What’s new

• Fusion MCP server is available at https://mcp.fusion.adobe.com/mcp for custom MCP integrations (Claude, ChatGPT, Copilot, Gemini, Cursor, VS Code, and others).
• Adobe Coworker now includes built‑in Fusion support (standalone Coworker and Coworker in the Fusion right rail). No custom MCP URL or OAuth app registration required for Coworker.
• All MCP tools described in the Fusion MCP tools reference are exposed to connected agents and follow the same read/write permissions as your Fusion role and team membership.

How to get started

Choose the surface you want to use:

• Coworker (recommended) — Open Coworker (standalone) or the Coworker panel in the Fusion right rail and ask Fusion‑related questions. Coworker uses your Adobe ID and Fusion permissions automatically. To test Coworker integrations: Customization > Integrations > find fusion-mcp > Test.
• Claude — Add Fusion as a custom connector and point it at https://mcp.fusion.adobe.com/mcp. (Claude Team/Enterprise owners can add custom connectors.)
• ChatGPT / other MCP clients — Add a custom MCP server of type Streamable HTTP and use https://mcp.fusion.adobe.com/mcp. Authenticate via OAuth when prompted.
• Custom agents — Connect directly to the MCP server URL from your MCP‑compatible agent implementation.

Permissions and safety

• The agent performs actions using your Adobe ID and your Fusion role/team permissions — it cannot access anything you don’t already have permission to view or change.
• Tools are labeled Read or Write; destructive operations always require explicit confirmation.
• Connection and key tools return metadata only (name, type, scopes, expiration). They do not expose secret values or credentials.

Admin checklist

• Ensure users and organizations are signed in with Adobe IDs (IMS).
• Enable MCP access for organizations that want agent integrations.
• Review and set Read vs Write MCP tool permissions for your teams.
• Confirm connected app callback URLs if you add custom OAuth apps for non‑Coworker integrations.

Troubleshooting (quick)

• No data visible? — Ask the agent to list organizations and switch to the correct organization (tools: fusion_orgs_list, fusion_orgs_set).

Feedback and support

If you have questions, find an issue, or want to request enhancements (for example, tailored tone templates for Coworker, additional safety confirmations, or org‑level presets), please:

• Send feedback straight from your AI assistant with the fusion_feedback_submit tool. Ask it to report a bug, flag a wrong result, request a feature or share praise (for example, "Send feedback to the Fusion team: the scenario list is missing folder names").
• Post in the Experience League Community thread for Fusion MCP/Coworker.
• Open a support ticket via the Admin Console Support portal for migration or access issues.

We’re excited to make Fusion accessible via conversational, agentic workflows. Try Coworker or add the MCP server to your preferred agent and let us know how it goes.