Adobe Workfront

Find, create, update and delete Workfront work items from an AI agent.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Adobe Workfront connector does

The Adobe Workfront MCP server connects a Workfront instance to Claude, ChatGPT and other MCP clients. An agent can search projects and tasks, create and update work items, manage Planning records and fields, move approvals through their stages, and email approvers who have not yet decided. Roughly half the documented surface writes, and an administrator toggle gates it.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Adobe Workfront tools (68)

  • approvals_find_document_version_by_name
  • approvals_get_document_by_version_id
  • approvals_get_documents_by_project
  • approvals_resolve_document_scope
  • approvals_get_approval_info
  • approvals_create_or_update_approval_workflow
  • approvals_create_approval_from_template
  • approvals_delete_approval_stage
  • approvals_send_reminder_to_participants
  • approvals_send_reminder_to_undecided
  • approvals_list_templates
  • approvals_search_template_by_name
  • approvals_create_template
  • approvals_update_template
  • approvals_get_current_user
  • approvals_find_user_by_name
  • approvals_find_team_by_name
  • approvals_find_project_by_name
  • approvals_get_projects_by_owner
  • approvals_get_adobe_region
  • planning_get_workspace
  • planning_get_workspace_list
  • planning_create_workspace
  • planning_create_workspace_from_template
  • planning_update_workspace
  • planning_delete_workspace
  • planning_convert_workspace_to_template
  • planning_get_workspace_sharing
  • planning_modify_workspace_sharing
  • planning_get_record_type
  • planning_create_record_types
  • planning_update_record_type
  • planning_delete_record_type
  • planning_list_global_record_types
  • planning_list_addable_global_record_types
  • planning_add_global_record_type_to_workspace
  • planning_remove_global_record_type_from_workspace
  • planning_get_external_record_workspaces
  • planning_get_record_type_sharing
  • planning_modify_record_type_sharing
  • planning_get_record
  • planning_search_records
  • planning_bulk_record_actions
  • planning_create_connection_record
  • planning_update_records_order
  • planning_get_record_change_log
  • planning_get_record_sharing
  • planning_modify_records_sharing
  • planning_get_field
  • planning_create_fields
  • planning_update_field
  • planning_delete_field
  • planning_get_view
  • planning_create_view
  • planning_update_view
  • planning_delete_view
  • planning_get_view_sharing
  • planning_modify_view_sharing
  • planning_get_template_list
  • planning_get_template
  • planning_search_resources
  • planning_search_sharing_data
  • planning_search_users
  • workflow_search_any_object
  • workflow_create_any_object
  • workflow_update_any_object
  • workflow_delete_any_object
  • workflow_resolve_field_names_any_object

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Writes are real and broad. Adobe classifies 44 of its 94 documented tools as Write, spanning create, update and delete across projects, tasks, issues, Planning schema, comments and approval structure. The directory's Read and write label is accurate, not cautious.
  • Two tools email your colleagues, with no documented confirmation step. The reminder tools are classified Write and dispatch to named approval participants. Adobe documents an explicit confirmation requirement for exactly one tool in the entire reference — object deletion — and the reminder tools are not it.
  • No documented reminder rate limit. Adobe publishes no cooldown, cap or de-duplication rule for reminders. Whether repeated calls send repeated emails is undocumented, and we did not test it.
  • Approval-stage deletion has no documented undo. Only not-started stages can be deleted, which is a real guard rail, but Adobe's reference describes no restoration path for one that has been.
  • The directory listing is inaccurate in both directions. It omits 18 documented tools including two whole families, and lists a tool Adobe recorded as removed on 13 August 2026 plus four Adobe marks deprecated.
  • We could not verify any of it from the wire. The endpoint returns 401 to an anonymous handshake, so no schemas, parameters or readOnlyHint / destructiveHint annotations were readable. Every safety classification here is Adobe's from its Read/Write column, not ours.
  • No sandbox boundary is documented. Unlike Adobe's Experience Platform connectors, Workfront's MCP documentation describes no isolation partition. The scoping is a profile and instance chosen once at sign-in and persisting until you disconnect.
  • Region handling is undocumented. approvals_get_adobe_region appears in the directory but in none of Adobe's tool tables, and no region or data-residency documentation exists for this server that we could find.
  • Planning is separately licensed. The largest family, 43 of 68 listed tools, requires a Workfront package that includes Adobe Workfront Planning.
  • AEM tools need a separate integration. Adobe states the Experience Manager tools require a native integration configured in your instance, and that sending documents to an AEM folder is not yet supported for projects on Adobe cloud storage.
  • Parallel-path approval tools are not generally available. Adobe's release banner marks that functionality as Preview-only, reaching Production monthly for organisations on fast releases.
  • Adobe disclaims responsibility explicitly. It states the platform acts using your account and permissions, that its actions have the same effect as your own, and that Adobe is not responsible for changes the platform makes to your Workfront data.
  • Stale context is a documented failure mode. Adobe warns that platforms may reuse earlier conversation data rather than re-querying, so an agent can act on an outdated picture of a work item.
  • The /v1 pin does not freeze the tool set. Adobe states new server versions are picked up automatically with no reconnection, so tools can be added or retired within v1.

Frequently asked questions

Can the Adobe Workfront MCP server delete projects and tasks?

Yes, if your administrator has turned writes on. Adobe documents delete tools for objects, fields, views, workspaces, record types and comments, and its own example prompts include deleting a project by name. Write MCP tools is a System Preferences toggle that ships disabled, so a fresh connection reads only until an administrator enables the write half.

Can an AI agent send reminder emails to my colleagues through Workfront?

Yes. Adobe documents two reminder tools that send emails to named approval participants, one targeting specific people and one targeting everyone still undecided. Both are classified Write. Adobe documents no per-send confirmation step for either, unlike the object delete tool, which it says requires explicit user confirmation before it runs.

What does the Workfront MCP server's planning family of tools actually reach?

Adobe Workfront Planning's whole schema layer, not just its data. The forty-three planning tools cover workspaces, record types, records, fields, views, templates and sharing. Twenty-three are writes, including deleting a field, which Adobe describes as permanently removing that field and all of its data from a record type. Planning needs a package that includes it.

Does the Adobe Workfront MCP server list the same tools that Adobe documents?

No, and the gap runs both ways. Anthropic's 2026-08-16 snapshot names sixty-eight tools; Adobe's reference table documents ninety-four across five families. The snapshot omits the entire insights and comment families, and it still lists a tool Adobe records as removed on 13 August 2026, three days before the snapshot was taken.

Which licence and admin settings do I need for the Workfront MCP server?

An active Workfront account, an instance enabled on Adobe Identity Management System, and administrator action. Adobe describes two System Preferences toggles: read-only MCP tools, enabled by default, and write MCP tools, disabled by default. Workfront Planning tools additionally need a package that includes Planning. Enterprise AI platforms need their own administrator to allow the connector.

What OAuth scopes does the Adobe Workfront MCP server request?

Eighteen, and they are broader than Workfront alone. The resource descriptor advertises Adobe identity scopes alongside product scopes for Experience Manager assets and folders, plus product-context and organisation reads. Unusually for an Adobe connector, the authorization server is the MCP host itself rather than the shared Adobe IMS login host, so this list is the connector's own.

Is deleting an approval stage through the Workfront MCP server reversible?

Adobe does not say, and that silence is the honest answer. It documents one guard rail instead: only stages that have not started can be deleted. Started, completed and locked stages are protected, and parallel paths keep at least one stage. Nothing in Adobe's tool reference describes undo, a recycle bin or restoration for a deleted stage.

Sources

  • Adobe Workfront MCP server overview — https://experienceleague.adobe.com/en/docs/workfront/using/basics/workfront-mcp-server/workfront-mcp-server-overview (last updated 12 June 2026; fetched 2026-08-19 as Markdown via the .md suffix; the directory's documentation URL returned 200 directly with no redirect) · retrieved 2026-08-19
  • Configure the Adobe Workfront MCP server — https://experienceleague.adobe.com/en/docs/workfront/using/basics/workfront-mcp-server/configure-workfront-mcp-server (last updated 12 June 2026; fetched 2026-08-19). Source of the two-administrator gating, the System Preferences toggles, and the Claude and ChatGPT connection flows · retrieved 2026-08-19
  • Use the Adobe Workfront MCP server — https://experienceleague.adobe.com/en/docs/workfront/using/basics/workfront-mcp-server/use-workfront-mcp-server (last updated 12 June 2026; fetched 2026-08-19). Source of the example prompts, the delete warning, the responsibility notice and the stale-context caution · retrieved 2026-08-19
  • Adobe Workfront MCP server tools — https://experienceleague.adobe.com/en/docs/workfront/using/basics/workfront-mcp-server/workfront-mcp-server-tools (fetched 2026-08-19). The Read/Write column, the 94-tool five-family census, the reminder and stage-deletion descriptions, and the deprecation and removal notes · retrieved 2026-08-19
  • Adobe Experience League machine index — https://experienceleague.adobe.com/llms.txt (version 1.8, 2026-08-05; fetched 2026-08-19), reached in documentation order: robots.txt then llms.txt then the .md suffix · retrieved 2026-08-05
  • experienceleague.adobe.com/robots.txt (last updated 2026-06-11; fetched 2026-08-19) allows all crawlers except /admin/ and /private/, names GPTBot, ClaudeBot and anthropic-ai blocks permitting AI training with a crawl delay of 5, and advertises the .md suffix in a comment. No Content-Signal line is present, so no use-side restriction is expressed · retrieved 2026-06-11
  • Live RFC 9728 protected-resource descriptor — https://mcp.workfront.adobe.com/mcp/v1/workfront/.well-known/oauth-protected-resource (fetched 2026-08-19; all three path forms return 200 and were diffed; only resource and authorization_servers differ between root and path-scoped forms) · retrieved 2026-08-19
  • Live RFC 8414 authorization-server metadata — https://mcp.workfront.adobe.com/.well-known/oauth-authorization-server (fetched 2026-08-19; the MCP host is its own authorization server, unlike the Journey Optimizer sibling) · retrieved 2026-08-19
  • Live anonymous probe — 2026-08-19: a single anonymous initialize POST to the endpoint returns HTTP 401 with a www-authenticate Bearer challenge naming realm workfront-mcp, invalid_token and resource_metadata; the OpenID configuration path returns 404. No tool was called and no authentication was attempted · retrieved 2026-08-19
  • Anthropic connector directory — https://claude.ai/directory/81d7db7c-e329-41ee-bc8e-48beceac2d68 (snapshot 2026-08-16; source of the 68 tool names, the Read and write permissions label, the partner tier, the productivity category, and an empty prompt list) · retrieved 2026-08-16
  • Adobe privacy policy — https://www.adobe.com/privacy/policy.html (per the directory snapshot, 2026-08-16) · retrieved 2026-08-16
  • Adobe Workfront customer support — https://experienceleague.adobe.com/en/docs/workfront/using/basics/tips-tricks-for-basics/contact-customer-support (per the directory snapshot, 2026-08-16) · retrieved 2026-08-16

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Agility CMS

    Model content, author pages and publish to a live site from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Adobe Workfront to work.

Connect Adobe Workfront once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio