Adobe Workfront remote MCP connector

The Adobe Workfront remote Model Context Protocol (MCP) connector in Mark (Optimizely Agent Platform) brings your Workfront projects, requests, approvals, planning records, and dashboards into Mark. Use Mark chat, agents, and workflows to manage work, approvals, and reporting from natural-language requests.

First, a Workfront administrator must enable AI and MCP access in Workfront, and then a Mark administrator must connect the Adobe Workfront remote MCP to Mark. After the administrator adds the MCP server, individual Mark users and agent builders log in to Workfront to access their data from Mark. Administrators only need to add the Adobe Workfront remote MCP once.

The following use cases show how you can use Workfront connector tools in Mark to speed up reviews, intake, experimentation planning, reporting, and launch readiness.

Goal – Move content through review faster and catch brand issues earlier.

Approval chain setup – Ask Mark to set up an approval chain on a project's documents, either from a reusable approval template or as custom stages, such as editor, brand, and legal. Add an AI Collaborator as a brand-compliance reviewer, and ask Mark to summarize its results so you can fix issues before people spend time on review.

Stalled approvals – Ask Mark to find approvals that have stalled and send bulk reminders to reviewers who have not decided. When a reviewer is out, Mark previews a reviewer change across all the project's documents and applies it after you confirm.

Example prompt: Set up our standard three-stage approval on the Q1 eBook draft, add the brand-compliance bot to the Brand stage, and remind anyone who has not responded.

Goal – Give web requests one queue and hand approved files to Adobe Experience Manager (AEM) without manual steps.

Complete request intake – Mark reads the request queue's form and asks you for each field, instead of guessing, before it submits the request. Larger requests, such as a landing page redesign, can be converted into a project with tasks and owners.

Backlog and handoff – Ask questions such as "What web requests are overdue or unassigned?" After creative is approved, send the files to an AEM folder, either a Workfront folder linked to AEM or a native AEM folder.

Example prompt: Submit a request to the Web Ops queue to update the pricing page hero, then show me all open web requests older than 10 days.

Goal – Keep test ideas, schedules, and results in one place.

Planning workspace – Ask Mark to set up a Planning workspace with record types such as hypotheses, experiments, and pages. Add a timeline view grouped by page to spot overlapping tests, and a calendar view for launch dates.

Ideas to results – Log friction points and funnel drop-offs from analytics connectors as hypothesis records in bulk. When an idea is approved, create a linked Workfront project for design and development tasks. After a test ends, add the results from Optimizely Experimentation to the record and post a comment that @mentions stakeholders.

Example prompt: Take the top five friction points from last week's analysis, log them as hypotheses in our Experimentation Roadmap, and show me any experiments overlapping on /pricing in December.

Goal – Answer "Are we on track for launch?" without assembling status by hand.

Delivery dashboard – Ask Mark to build a Reporting dashboard with KPI tiles for overdue tasks and open approvals, a chart of task status by portfolio, and a table of at-risk projects.

Ad hoc questions and summaries – Ask which campaigns are behind schedule, or compare planned and actual hours. Mark can write a summary of each flagged project for a weekly update.

Example prompt: Build a Campaign Ops dashboard showing overdue tasks, tasks by status per portfolio, and pending approvals, then summarize the three most at-risk projects.

Goal – Find launch blockers before launch week.

Scheduled readiness check – Build a scheduled multi-agent workflow that fetches projects due in the next 14 days along with unassigned or overdue tasks and stalled approvals. It then ranks blockers by how close the launch is, sends approval reminders, posts comments that @mention owners, and sends a digest to Slack or an Opal board.

Before a Mark administrator connects Workfront, a Workfront administrator must complete the following steps in Workfront:

The first person to connect a third-party service to Mark should be an administrator of that service. Administrator access installs the complete set of tools, so Mark adds every available tool. If a non-administrator connects the service first, Mark installs only the tools that account can access.

As a Mark administrator, complete the following steps:

A confirmation message displays, and you can close the pop-up window.

After adding the Adobe Workfront connection, Mark prompts you to select which tools to enable and optionally customize their display names.

As a Mark administrator, complete the following steps:

The Adobe Workfront tile displays Connect on the Connectors tab for Mark users to authenticate with their personal accounts.

To update the available tools or names, see Update tools.

Each Mark user and agent builder logs in to Workfront individually to access their data from Mark. User-level authentication ensures you access only the data your Workfront account is authorized to view.

Before you begin, confirm that a Mark administrator has connected the Adobe Workfront remote MCP to Mark. Until an administrator connects it, the Adobe Workfront tile displays Contact admin instead of Connect and you cannot select it.

To authenticate, complete the following steps in Mark:

After you log in, the Workfront connector tools are available in Mark chat, agents, and workflows.

The available tools depend on which tools your administrator enabled. For the full list of tools, see the Workfront MCP server tools in the Adobe Experience League documentation.

The Workfront connector tools are grouped into the following categories:

To rename, add, or remove tools, a Mark administrator must delete the Adobe Workfront tools registry and re-add it. Complete the following steps: