Expose project-specific Tempo Team options and hierarchy in Atlassian MCP

Question

Hi Atlassian team,

I use the Atlassian MCP server to create Jira Stories and need to assign each Story to the correct Tempo Team. The MCP can create Stories, but it doesn’t appear to provide an authoritative list of the Tempo Team options available for a project, or their parent-child relationships.

Could MCP provide a project- and issue-type-specific lookup for Tempo Team options, including stable IDs and hierarchy, and allow a Story to be assigned to a selected Tempo Team during creation? This is about the Tempo Team field, not the separate Atlassian Teams directory.

Without this, I have to use Jira’s UI to find the correct team and create or update the Story manually.

Jason David · Answer

Thanks for the suggestion! I'll give it a shot.

Mihai_LeanZero · Answer

Hi @Jason David,

The thing to check is the Tempo REST API. It uses its own token, so the Tempo MCP switch doesn't matter.

Tempo Team is an app field, so the team ids come from Tempo's own API. You can create a personal token under Tempo > Settings > Data Access > API integration (it sees what your Tempo permissions see) and send it as a Bearer token.

1. GET /4/team-links/project/{projectId} returns the teams linked to that space, each with id and name. It takes the numeric project id, not the key.
2. The Story gets that id in the Tempo Team field at creation, as a string like "2". Names won't work. Tempo's own KB covers this, search for "set a Tempo team on Jira issue".

There are no parent and child teams in Tempo. The grouping is Programs, and GET /4/programs/{id}/teams lists the teams in each.

I couldn't find anything from Atlassian about app fields like this coming to their MCP, so I wouldn't wait on it. Try it on one test Story first.

Narek Pirumyan · Answer

I don't think it would be available from Atlassian MCP since Tempo is just a marketplace app. Though there were some announcements that I heard during the last Team Europe that forge apps data will become available to rovo and queriable via the teamwork grapgh, but I'm not sure to what extent it will cover your use case and when it will be implemented.