Add teamwork.com mcp server

[Rhys Gottwald]

Good afternoon, everyone.

Good afternoon, everyone. I’m trying to add the Teamwork.com MCP server in my Rovo studio, but I keep getting this error.

Is there anything I can do to resolve it on my own?

[Rhys Gottwald]

I got this from Teamwork

Unfortunatly there is no update at the moment. Our team are waiting on Atlassian to follow up to provide an OAuth flow redirect that we can whitelist on our MCP server. I do apologise, but until this is provided, there will not be a way to resolve this. As soon as we hear back from them, we will let you know.

[Rhys Gottwald]

Hi everyone, this is the feedback I got from Atlassian Support that's now with Teamwork Support. Hi everyone, this is the feedback I got from Atlassian Support that's now with Teamwork Support. 

What we found:
When you attempt to add the MCP server, Atlassian Rovo tries to automatically register as an OAuth client with Teamwork.com using a process called Dynamic Client

Registration (DCR).
The logs show that our request to Teamwork's registration endpoint (https://www.teamwork.com/developer/api/v1/apps/register.json) is being rejected by their server with a 400 Bad Request error:

• Error Code: MCP_SERVER_REGISTRATION_OAUTH_DCR_REJECTED
• Message: Failed to register OAuth client: 400 Bad Request from POST 

Next Actions:
Since the rejection is coming directly from the Teamwork.com side, we recommend sharing these specific details with their support or development team:

1. Provide the Error Detail: Inform them that the Atlassian Rovo registration is failing at their /developer/api/v1/apps/register.json endpoint with a 400 error.
2. Confirm DCR Compatibility: Ask if their MCP server implementation supports the standard OAuth 2.0 Dynamic Client Registration (RFC 7591) flow.
3. Identify Missing Requirements: Check if there are any specific mandatory fields, headers, or pre-approvals required by their API that might be causing the "Bad Request" rejection.

Reference document to add an external MCP server: https://support.atlassian.com/organization-administration/docs/add-an-external-mcp-server-from-atlassian-administration/
Once Teamwork.com provides more information on why the endpoint is rejecting the registration request, please let us know so we can assist further.
If any further queries, please let me know.

[Tomislav Tobijas]

Thanks for sharing this @Rhys Gottwald !

It's kinda interesting to see how this story will end 😅
I'm keen to see what Teamwork team will say on this 👀

[Rhys Gottwald]

@Tomislav Tobijas is there anything I can do to speed this process up?

[Tomislav Tobijas]

@Rhys Gottwald Hmmm... What you could try is to reach out to the support team. This is the official channel for Rovo and Rovo MCP now: Atlassian Support

They will probably have some additional insights and see if that's something they are planning to add (or if there's any workaround you could use). 👀

I did try to check JAC and if there's an open suggestion related to this, but couldn't find anything. 😕

[Rhys Gottwald]

Thanx Tomislav, I did try take this to Support but because we are on Rovo free it sent me here.

[Rebekka Heilmann _viadee_]

@Rhys Gottwald yep that's a little annoying that Rovo sometimes is listed as free product. Simply choose another product that is on a paid plan and explain in the description that this is Rovo related

[Rhys Gottwald]

I've raised a support ticket. I'll see what they come back with. I've raised a support ticket. I'll see what they come back with.