Enabling this Adobe Workfront MCP integration makes Workfront available to Studio Task Agents in the Jasper workspace.
Three admins are needed to set this up.
- The Adobe organization administrator creates the credential.
- The Workfront administrator decides what that credential can do in Workfront.
- The Jasper workspace admin enters four values from that credential into Jasper.
Who does what
| Role | What they do |
|---|---|
| Adobe IMS organization administrator | Creates the Developer Console project and the OAuth Server-to-Server credential. A Workfront product administrator, or someone with only the Adobe Admin Console Developer role, cannot complete this part. |
| Workfront administrator | Sets the technical account's access, shares the Workfront items Jasper should use, and turns on the Workfront MCP switches. |
| Jasper workspace admin | On Adobe Workfront, turns on Workspace connection and enters the four values. |
The Jasper form asks for these four values:
- Client ID
- Client Secret
- Adobe scope
- Workfront domain
Copy them while you are in Adobe Developer Console. The Jasper workspace admin pastes them in Jasper.
Before you start
- Confirm the Workfront instance is enabled on Adobe IMS. Ask your Workfront administrator if you are not sure. Workfront MCP requires it.
- Use the production Workfront instance, the one your team uses day to day. Its hostname looks like company.my.workfront.com. Preview is Adobe's separate test copy, at company.preview.workfront.com, and Jasper's Workfront domain field accepts the production hostname.
- Have the Workfront administrator available for the technical account and the MCP switches.
Workfront credential setup guide, including screenshots
1. Create the project
The Adobe IMS organization administrator does this in Adobe Developer Console.
You will copy four values from the credential you create below: Client ID, Client Secret, Adobe scope, and Workfront domain. The Jasper workspace admin enters those in Jasper.
- Sign in to Adobe Developer Console.
- Confirm you are in the Adobe organization that owns the Workfront instance.
- Create a new Project.
- Name it so the connection is obvious, for example Jasper – Workfront MCP – Production.
2. Add Adobe Workfront
The same Adobe IMS organization administrator does this section and the next two.
- In the project, click Add API, or + Add to Project → API.
- Find Adobe Workfront under Experience Cloud.
- Select it and click Next.
Workfront's Planning, Workflow, and Review and Approvals APIs are grouped under the single Adobe Workfront API. Workfront Planning tools also require a Workfront package that includes Adobe Workfront Planning.
3. Configure OAuth Server-to-Server
- Select Server-to-Server / OAuth Server-to-Server.
- If prompted, name the credential, for example Jasper Workfront MCP S2S – Production.
- If more than one instance is listed, select the production instance.
- If a product-profile selection screen appears, select the profile or profiles for the production instance. You still choose which projects and documents Jasper can open when you set up the technical account.
- Click Save configured API.
Configure the API and credential
4. Copy the four values
Open the OAuth Server-to-Server entry under Credentials. Click Retrieve client secret where it is shown. These four values are what the Jasper workspace admin enters later.
| Jasper field | What to copy |
|---|---|
| Client ID | Client ID on the credential. |
| Client Secret | The secret from Retrieve client secret. Store it in your team's password manager, and have the Jasper workspace admin enter it in Jasper. |
| Adobe scope | The scope value from the credential's generated token request. Copy that string exactly, commas included. Jasper uses it to request the access token. |
| Workfront domain | The hostname of the instance you selected, for example tenant.my.workfront.com. Hostname only. Leave off https:// and any path. |
The Technical Account Email on this same page is for the next step. Jasper does not ask for it.
Optional: click Generate access token on the credential page. A token confirms Adobe accepted this credential. Jasper requests its own token from the Adobe scope you copy into the form.
Credential details · Workfront technical account
5. Set what the technical account can do
The Workfront administrator does this.
Enabling Adobe Workfront MCP lets Jasper’s Studio Task Agents use this connection. The Jasper workspace acts as one Workfront user: this technical account. Anyone in the Jasper workspace who runs a Task Agent against Workfront acts as that same Workfront user. Its access level, and the projects, tasks, and documents shared with it, are what Jasper can open and change.
- In Workfront, search users for techacct.
- Open the user whose email matches the credential's Technical Account Email. Other API clients can create more than one techacct user.
- Set its access level, and share or assign the Workfront items Jasper should use.
Adobe starts this user as a Contributor with limited access. A working credential still sees only the items shared with this user.
Give this user Workfront administrator access only when Jasper needs an admin-only action. In Adobe Admin Console, add the technical account email as an administrator of the product profile for the production instance.
6. Turn on the Workfront MCP switches
The Workfront administrator does this. The switches are in Workfront, separate from the technical account's access.
- In Workfront, open the Main Menu, then Setup.
- Open System → Preferences.
- Confirm Read-only MCP tools is on. Adobe turns this on by default. Task Agents need it to read Workfront.
- Turn on Write MCP tools. Adobe leaves this off. With it on, Jasper can create, update, or delete Workfront items, including exporting content from Jasper into Workfront.
Configure the Adobe Workfront MCP server · System preferences
7. Connect it in Jasper
The Jasper workspace admin does this. Paste the four values from the Developer Console credential.
Adobe Workfront is one row. Workspace connection is this shared connection, and Studio Task Agents use it. User connections is a different switch on that same row. Turning that on opens a different Workfront form, for each person to connect their own account.
- In Jasper, go to Settings → Admin controls → Team integrations.
- On Adobe Workfront, click Manage.
- In Manage access to Adobe Workfront, turn on Workspace connection.
- Connect to Adobe Workfront opens. Enter:
| Form field | What to enter |
|---|---|
| Client ID | Client ID from the credential. |
| Client Secret | Client secret from the credential. |
| Adobe scope | The scope string copied from the credential's generated token request. |
| Workfront domain | The instance hostname, for example tenant.my.workfront.com. |
- Click Save.
To use Workfront with a Studio Task Agent:
On the Studio Task Agent, add Adobe Workfront and enable the tools that agent should use.
If something doesn't work
| What you see | What to check |
|---|---|
| Workfront cannot be selected, or Server-to-Server is unavailable | The Adobe organization, the Workfront entitlement, and a full IMS organization administrator. |
| Jasper rejects the Workfront domain | A bare hostname ending in .my.workfront.com, such as tenant.my.workfront.com. |
| You are looking for a Connect button for Adobe Workfront MCP | Open Team integrations, click Manage on Adobe Workfront, and turn on Workspace connection. The Integrations page shows status and has no Connect button for this. |
| The Adobe Workfront row says connected for workspace, and a Task Agent cannot read Workfront | Client ID, Client Secret, and the exact Adobe scope. Then the instance on Adobe IMS, Read-only MCP tools, and the technical account's access to that item. |
| Jasper can find Workfront items and cannot create or update them | Write MCP tools under Setup → System → Preferences, and the technical account's permission to change that item. |
| Jasper is looking at the wrong Workfront data | The instance selected on the credential, and the Workfront domain entered in Jasper, are the same instance. |
Done when
- The project has Adobe Workfront and an OAuth Server-to-Server credential.
- The production instance is selected.
- If a product-profile screen appeared, the profile for that production instance is selected.
- The client secret is in Jasper.
- The technical account can open the Workfront items Jasper should use.
- Read-only MCP tools is on.
- Write MCP tools is on, so people can export content from Jasper into Workfront.
- Workspace connection is on for Adobe Workfront, and the row says connected for workspace.
- Client ID, Client Secret, Adobe scope, and Workfront domain are saved in Jasper.
- On the Studio Task Agent, the Adobe Workfront tools it needs are enabled, and it can read a Workfront item this technical account can open.
Older Workfront OAuth2 applications
Create this connection in Adobe Developer Console. The older path is Workfront Setup → System → OAuth2 Applications. Adobe stops new applications there on November 1, 2026, and existing applications stop working on February 1, 2027.
An application already created on that older path is a separate connection. This project is the one Jasper uses for Adobe Workfront MCP.