Adobe Workfront MCP server tools
The highlighted information on this page refers to functionality not yet generally available. It is available only in the Preview environment for all customers. After the release to Preview, the same features are also available monthly in the Production environment for customers who enabled fast releases.
For information about fast releases, see Enable or disable fast releases for your organization.
This article lists the tools that the Adobe Workfront MCP server exposes to a connected AI agentic platform. The platform calls these tools on your behalf when you ask it to find, create, update, or delete Workfront items.
For information about how to use these tools through an AI agentic platform, see Use the Adobe Workfront MCP server. For information about how to set up the connection, see Configure the Adobe Workfront MCP server.
How product entitlements affect the tool list
The tools that appear in your AI agentic platform depend on your organization’s Workfront product entitlements.
- Customers licensed only for Workfront Planning see Planning tools, but not Workflow tools.
- Customers licensed only for Workfront Workflow see Workflow tools, but not Planning tools.
- Customers licensed for both Workfront Workflow and Workfront Planning see both sets of tools.
- Insights and context tools are available to all customers.
If your organization is not entitled to a product area, the related tools do not appear in the tool list for that connection. If an AI agentic platform attempts to call a tool that is not available for your entitlements, the request is blocked.
The following tables identify the product area each tool belongs to.
Toolsets in the Workfront MCP server
For information and instructions, see Configure the Adobe Workfront MCP server
Toolsets let you select the Workfront capabilities your AI client needs instead of exposing the full MCP catalog. This is useful for clients that load all tool definitions up front, need to stay within tool-count limits, or benefit from a more focused tool list.
You can specify toolsets by adding the toolsets query parameter to the Workfront MCP server URL.
Example:
https://mcp.workfront.adobe.com/mcp/v1/workfront?toolsets=core,comment-stream
This example exposes the core and comment-stream capabilities. The core group is automatically included whenever a subset is selected.
Available toolsets include:
core: The base Workfront toolset that is included automatically when you select a subset of toolsets.comment-stream: Tools for comment and discussion workflows.planning: Tools for Workfront Planning capabilities.approvals: Tools for approval workflows.reporting: Tools for reporting.
To expose the full authorized catalog, omit the parameter or use toolsets=all.
You can Combine optional groups with commas, such as toolsets=core,planning,approvals.
Selection applies to tools, resources and resource templates, prompts, and MCP apps that surface Workfront tools in their UI. Backend-specific server instructions follow the selected toolset configuration as well.
Toolsets do not change permissions. Your Workfront access level and object permissions continue to be enforced.
If you want the AI client to access a different domain, update the connection configuration to select the appropriate toolset.
Read and write actions
Each tool in the following tables is classified in the Action column as either a Read or Write action:
- Read: Retrieves information from Workfront without changing your data. For example, finding a project, listing documents, or getting a record’s details.
- Write: Creates, updates, or deletes Workfront data. For example, creating a project, updating a record, or deleting a view.
Your Workfront administrator controls which categories of tools the AI agentic platform can use through two toggles in System Preferences:
- Read-only MCP tools (enabled by default)
- Write MCP tools (disabled by default)
If the AI agentic platform can find Workfront items but can’t create, update, or delete them, ask your Workfront administrator to enable write actions. For more information, see Admin prerequisites in Configure the Adobe Workfront MCP server.
Approvals tools
Product requirement: All customers
There are currently no entitlement limitations on approvals tools.
Documents
upload_document_uiapprovals_find_document_version_by_nameapprovals_get_document_by_version_idapprovals_resolve_document_scopeapprovals_get_documents_by_scopeinsights_find_workfront_data instead. This tool listed documents inside a project or folder.approvals_list_aem_linked_foldersapprovals_find_documentinsights_find_workfront_data instead. This tool looked up a document by filename or document version ID.approvals_send_documents_to_aem_folder*You must have a native Adobe Experience Manager integration configured in your Workfront instance to use these tools. For more information, see Overview of Adobe Experience Manager Assets integrations.
*Sending documents to an AEM folder is not yet supported for projects on Adobe cloud storage. Support is expected in a future release.
**This tool opens an interactive upload panel in the chat, so it only works in tools that support MCP Apps. Currently, only Claude is supported for this tool. It appears under “Interactive tools” in the tool permissions and asks for approval by default.
Approval workflows
approvals_get_approval_infoapprovals_create_or_update_approval_workflowapprovals_create_approval_from_templateapprovals_delete_approval_stageapprovals_add_path_to_approvalapprovals_remove_path_from_approvalapprovals_add_stage_to_pathapprovals_remove_stage_from_pathapprovals_reorder_stages_in_pathReminders
approvals_send_reminder_to_participantsapprovals_send_reminder_to_undecidedApproval templates
approvals_list_templatesapprovals_search_template_by_nameapprovals_create_templateapprovals_update_templateapprovals_send_approval_reminderapprovals_update_templateapprovals_update_approval_participants and approvals__submit_update_approval_participantsLookups and users
approvals_find_project_by_nameinsights_find_id_by_name instead. This tool looked up Workfront projects by partial name match across the system.approvals_get_projects_by_ownerinsights_find_workfront_data instead. This tool listed Workfront projects where the calling user was the owner.approvals_get_current_userapprovals_find_user_by_nameinsights_search_users instead. This tool looked up a Workfront user’s ID by name (fuzzy or partial match), returning name, ID, email, title, and avatar URL.approvals_find_team_by_nameinsights_find_id_by_name instead. This tool looked up a Workfront team’s ID by name (fuzzy or partial match).approvals_find_projectsinsights_find_workfront_data instead. This tool looked up Workfront projects, optionally filtered by name and/or restricted to projects the calling user owns.Planning tools
Product requirement: Workfront Planning
- To use MCP with Workfront Planning, your organization must be on a Workfront package that includes Adobe Workfront Planning.
Workspaces
planning_get_workspaceplanning_get_workspace_listplanning_create_workspaceplanning_create_workspace_from_templateplanning_update_workspaceplanning_delete_workspaceplanning_convert_workspace_to_templateplanning_get_workspace_sharingplanning_modify_workspace_sharingRecord types
planning_get_record_typeplanning_create_record_typesplanning_update_record_typeplanning_delete_record_typeplanning_list_global_record_typesplanning_list_addable_global_record_typesplanning_add_global_record_type_to_workspaceplanning_remove_global_record_type_from_wsplanning_get_external_record_workspacesplanning_get_record_type_sharingplanning_modify_record_type_sharingRecords
planning_get_recordplanning_search_recordsplanning_bulk_record_actionsplanning_create_connection_recordplanning_update_records_orderplanning_get_record_change_logplanning_get_record_sharingplanning_modify_records_sharingFields
planning_get_fieldplanning_create_fieldsplanning_update_fieldplanning_delete_fieldViews
planning_get_viewplanning_create_viewplanning_update_viewplanning_delete_viewplanning_get_view_sharingplanning_modify_view_sharingTemplates
planning_get_template_listplanning_get_templateSearch & utilities
planning_search_resourcesplanning_search_sharing_dataplanning_search_usersWorkflow tools
Product requirement: Workfront Workflow
Workflow tools are the general-purpose actions the AI agentic platform uses to work with any Workfront object — projects, tasks, issues, hours, assignments, programs, portfolios, and so on.
Objects and fields
workflow_search_any_objectworkflow_create_any_objectworkflow_update_any_objectworkflow_delete_any_objectworkflow_resolve_field_names_any_objectworkflow_read_workflow_docsUpdate object tool abilities
The Update object tool does more than change field values. It can also relocate work between projects, promote work items into new objects, and wire up task dependencies.
Move a task or issue to another project
Moving reparents a work item in place. The object keeps its identity and links, it just lives in a different project or parent task.
- Move a task: Moves the task to a target project, and optionally under a target parent task.
- Move an issue: Moves the issue (request) to a target project.
Example prompts:
- “Move task Wireframes to the Mobile App Redesign project.”
- “Move this request under the Q4 Launch project.”
Convert an issue or task into a project
- Convert a task to a project: Creates a new project from the task. You can optionally copy the task’s custom data and base the new project on a project template.
- Convert an issue (request) to a project: Creates a new project from the issue. You can optionally copy the issue’s custom data, copy its native field values, and apply a project template.
- Convert an issue (request) to a task: Creates a task on an existing project from the issue.
Each conversion returns the newly created object, along with a link so you can open it directly in Workfront.
Example prompts:
- “Convert task Website Refresh into a project called Website Refresh 2026 using our standard template.”
- “Turn this request into a project and copy over its custom fields.”
Set task predecessors (dependencies)
You can define a task’s predecessors. Predecessors support the following dependency types, plus optional lag time:
- Finish-Start (FS): The task starts when its predecessor finishes. (Default)
- Start-Start (SS): The task starts when its predecessor starts.
- Finish-Finish (FF): The task finishes when its predecessor finishes.
- Start-Finish (SF): The task finishes when its predecessor starts.
You can add lag (a delay) or lead (a negative delay) in workdays, chain multiple predecessors on a single task, and reference a task in a different project.
Example prompts:
- “Make Development start after Design finishes.”
- “Set QA to start when Development starts, with a two-day lag.”
- “Add task #3 and task #5 as predecessors of Launch.”
Comments
comment-stream_query_commentscomment-stream_get_commentcomment-stream_get_comments_countcomment-stream_create_commentcomment-stream_create_replycomment-stream_update_commentcomment-stream_delete_commentcomment-stream_add_reactioncomment-stream_remove_reactionInsights tools
Product requirement: Workfront Workflow or Workfront Planning.
Insights tools retrieve information about Workfront objects.
insights_read_docsinsights_get_current_userinsights_search_fieldsinsights_get_field_pathsinsights_find_id_by_nameinsights_find_workfront_datainsights_summarize_objectinsights_list_entitiesinsights_search_usersFeedback tools
Product requirement: Workfront Workflow or Workfront Planning.
Feedback tools let you report your experience with the Workfront MCP server directly from your AI agentic platform.
share_feedbackReporting tools
Product requirement: All customers
Reporting tools let you build and manage Canvas Dashboards through chat. Describe the report you want in plain language, and the AI agentic platform creates the dashboard and widgets for you using your Workfront data.
Canvas Dashboards
reporting_relist_dashboardsview values "my", "shared", "all", and "favorites". Returns dashboard metadata only, including a URL to open each dashboard.reporting_get_dashboardreporting_get_widget{id, label, dataType} so they can be reused directly in the reporting_update_*_widget tools. Supported content types are Table, KPI, and MultiSeries.reporting_create_dashboardreporting_update_dashboardignoreDashboardFilters and layout settings. Omitted fields are left unchanged, and prompt and filter are fully replaced when provided.reporting_create_table_widgetget_widget shape.reporting_update_table_widgetreporting_create_kpi_widgetget_widget shape.reporting_update_kpi_widgetfieldId and aggregation are required, and the underlying report is fully replaced.reporting_create_chart_widgetreporting_update_chart_widgetaggregationFieldId, aggregationType, groupByFields, and chartType are required, and the underlying report is fully replaced.reporting_copy_widgetreporting_copy_dashboardreporting_delete_objectHow tools are updated
When Adobe releases a new version of the Workfront MCP server, the AI agentic platform uses the updated tool set automatically.
The tool list is set when the connection starts. If your organization’s product entitlements change, the updated tool list appears the next time you start a new connection to the Workfront MCP server.
Intent telemetry
Workfront MCP server tracks user intent for customers. Intent data gathered is generic for telemetry purposes, and only ever gathered for the intent of a user as it relates to the Workfront product. Prompt intent telemetry is only used to improve existing MCP tools in order to provide more accurate responses.
Users can disable telemetry collection by reaching out to customer support to file a request.
Additional tools coming soon
We are working on adding the following tools to the Workfront MCP server in the future:
- Boards