Can AI agents automate Adobe Workfront?
Adobe · saas · project-managementwork-managemententerprise
Adobe Workfront is automatable today through its REST API. This record is the Workfront work-management product (projects, tasks, issues, approvals, and Planning records), including the first-party MCP at https://mcp.workfront.adobe.com/mcp/v1/workfront. It is not Adobe Experience Manager, Adobe Workfront Fusion, Jira, or Asana. The API uses REST over HTTP with JSON responses on paths such as /attask/api/v15.0/project/{id}. Current API credentials are created in Adobe Developer Console as Server-to-Server OAuth. That setup needs a full IMS Org admin, not only a Workfront product admin. The technical account is added as a Workfront user with Contributor access until an admin raises it. Workfront no longer recommends /login or API keys. The Event Subscription API POSTs object changes to a customer HTTPS endpoint, typically in under five seconds. First-party MCP requires an IMS-enabled instance. A Workfront administrator must enable read tools (on by default) and write tools (off by default). Interactive clients use Adobe ID or OAuth; ChatGPT Desktop uses Streamable HTTP. Custom OAuth for arbitrary agents is not yet self-service; service-to-service callers send a Bearer IMS token. Official language SDKs, a product CLI, and iPaaS catalogs were not established from the opened pages. Computer-use viability is unassessed. API scores 8 and is the best path because it is the broader production surface; MCP is official and useful but write-gated and IMS-gated.
Best path today: api · Overall automatability: 8/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | restoauth2-server-to-server coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | yes | verdict: official |
| Integrations | unknown | |
| CLI | unknown | |
| Extensibility | yes | webhooks: True |
| Data access | export: unknown · import: unknown | |
| RPA / UI automation | unknown | web-dom No repeatable UI probe was run. Workfront's REST API, Event Subscription webhooks, and the Adobe-hosted MCP cover project and task automation without browser control. This record is not Adobe Workfront Fusion.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 8 | 7 | — | — | — | — | 8 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-09-20 |
license | declared | source | 2026-09-20 |
modalities.api.exists | declared | source | 2026-09-20 |
modalities.api.kinds[0] | declared | source | 2026-09-20 |
modalities.api.auth[0] | declared | source | 2026-09-20 |
modalities.api.coverage | declared | source | 2026-09-20 |
modalities.api.docs | declared | source | 2026-09-20 |
modalities.mcp.first_party | declared | source | 2026-09-20 |
modalities.mcp.verdict | declared | source | 2026-09-20 |
modalities.extensibility.webhooks | declared | source | 2026-09-20 |
modalities.agent_docs.llms_txt | declared | source | 2026-09-20 |
verdict.scores.api | declared | source | 2026-09-20 |
verdict.scores.mcp | declared | source | 2026-09-20 |
freshness.watch[0].url | declared | source | 2026-09-20 |
freshness.watch[1].url | declared | source | 2026-09-20 |
freshness.watch[2].url | declared | source | 2026-09-20 |
freshness.watch[3].url | declared | source | 2026-09-20 |
Related tools
Other products in this database that share a category with Adobe Workfront.
Last verified 2026-09-20 · volatility high · JSON record