Adobe Workfront earns its Atlas place through a hosted MCP spanning workflow, Planning, approvals, documents, comments, reporting, and authorized actions in supported AI clients.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Projects, tasks, issues, assignments, hours, programs, portfolios, comments, documents, approval workflows and templates, plus entitled Workfront Planning workspaces, record types, records, fields, views, sharing, and change logs.
Search and aggregate Workfront objects and fields; inspect comments, documents, approvals, users, teams, Planning structures, sharing, and record history using the connected user's access.
Create, update, or delete workflow and Planning objects; manage comments, approval stages, templates, reminders, participants, sharing, and bulk records when an administrator enables Workfront MCP write tools.
The instance must use Adobe IMS. Each connection authenticates a Workfront user and inherits that user's access level and object permissions; Workfront administrators separately enable read and write tool categories.
Read-only tools are enabled by default and write tools disabled by default. Keep writes selectively enabled, identify objects by stable IDs, refresh data before acting, and confirm delete, bulk, sharing, approval, or notification actions.
Current availability is limited to AWS-hosted Workfront customers. Planning tools require a package containing Workfront Planning, Boards tools are only announced as coming soon, and client platforms may cache conversational data.
First-party access
Agent access
Support: Official MCP server
Read scope: Query workflow objects, fields, aggregates, comments, documents, approvals, users, teams, and entitled Planning structures or history under the connected user's permissions.
Write scope: When administrators enable writes, create, update, delete, share, comment on, approve, or bulk-manage supported workflow and Planning records, and send approval reminders.
Authentication: Adobe IMS login connects an MCP-compatible client to one Workfront instance as a specific user, with the user authorizing access through the selected AI platform connection.
Approval boundary: Keep write MCP tools disabled by default and require explicit confirmation for create, update, and delete.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Adobe ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
MCP objects, reads, writes, confirmation behavior, permissions, and upcoming Boards tools
Workfront MCP tool families, action classes, and permission controls reviewed 2026-07-22
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
hosted MCP endpoint, IMS authentication, client compatibility, and administrator controls
Workfront MCP deployment, IMS, and admin gates reviewed 2026-07-22
availability, Planning entitlement, user permissions, confirmation, stale context, and data handling
Workfront MCP availability, data handling, and user boundary reviewed 2026-07-22
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
