Hi,
We're integrating the Adobe Workfront MCP server (https://mcp.workfront.adobe.com/mcp/v1/workfront) into our platform, Von, so that our mutual customers can connect their own Workfront instance and work with their Workfront data through our product simialr to how claude does with MCP connector.
What's happening:
When we attempt to connect via OAuth, Dynamic Client Registration (DCR) fails with an error indicating our redirect URI "is not allowed." Based on your configuration docs, it appears the MCP server currently supports pre-registered platforms (Claude, ChatGPT), and third-party clients require their redirect URI to be explicitly allowlisted before the OAuth flow will succeed.
(Reference: https://experienceleague.adobe.com/en/docs/workfront/using/basics/workfront-mcp-server/configure-workfront-mcp-server)
What we need:
Could you please allowlist our redirect URI so our OAuth flow can complete:
Here is our redirect URI pattern- http://auth.vonlabs.ai/sso/v1/oauth/conn_*/callback
(We can also provide the exact callback URL(s) for our production and test connections — happy to share whichever format you need.)
A few questions to make sure we set this up correctly:
Is redirect-URI allowlisting the correct path for a third-party platform like ours, or is there any other process.
Once allowlisted, will DCR complete automatically, or will you also issue us a client ID and secret to configure on our side?
Are there any requirements or restrictions for third-party integrations connecting to the Workfront MCP server (approval, plan requirements, regions)?
For context: Von is an AI platform used by revenue and customer-success teams. Each of our customers authenticates with their own Adobe/Workfront credentials, and access stays scoped to their own instance and permissions — this is a standard multi-tenant integration where customers connect their own accounts.
Thanks for your help,
Issue in .https://github.com/AdobeDocs/workfront.en/help/quicksilver/workfront-basics/workfront-mcp-server/configure-workfront-mcp-server.md
Hi,
We're integrating the Adobe Workfront MCP server (https://mcp.workfront.adobe.com/mcp/v1/workfront) into our platform, Von, so that our mutual customers can connect their own Workfront instance and work with their Workfront data through our product simialr to how claude does with MCP connector.
What's happening:
When we attempt to connect via OAuth, Dynamic Client Registration (DCR) fails with an error indicating our redirect URI "is not allowed." Based on your configuration docs, it appears the MCP server currently supports pre-registered platforms (Claude, ChatGPT), and third-party clients require their redirect URI to be explicitly allowlisted before the OAuth flow will succeed.
(Reference: https://experienceleague.adobe.com/en/docs/workfront/using/basics/workfront-mcp-server/configure-workfront-mcp-server)
What we need:
Could you please allowlist our redirect URI so our OAuth flow can complete:
Here is our redirect URI pattern- http://auth.vonlabs.ai/sso/v1/oauth/conn_*/callback
(We can also provide the exact callback URL(s) for our production and test connections — happy to share whichever format you need.)
A few questions to make sure we set this up correctly:
Is redirect-URI allowlisting the correct path for a third-party platform like ours, or is there any other process.
Once allowlisted, will DCR complete automatically, or will you also issue us a client ID and secret to configure on our side?
Are there any requirements or restrictions for third-party integrations connecting to the Workfront MCP server (approval, plan requirements, regions)?
For context: Von is an AI platform used by revenue and customer-success teams. Each of our customers authenticates with their own Adobe/Workfront credentials, and access stays scoped to their own instance and permissions — this is a standard multi-tenant integration where customers connect their own accounts.
Thanks for your help,
Issue in .https://github.com/AdobeDocs/workfront.en/help/quicksilver/workfront-basics/workfront-mcp-server/configure-workfront-mcp-server.md