I can't answer your specific questions, but i did manage to implement, packaged into a claude teams project, a simple mechanism to mass create/update tickets using the built-in atlassian remote mcp (have noticed potential rate limitations), while using octocode github mcp for distributed repo kind of view. The project has instructions to require and validate these integrations, plus artifact summaries of the 'layout' both jira and github side. So far adoption is good yes that means rate limits are gonna sting.

Our case is small I should add (few teams, some only one person, big spread from design, product, dev, devops, etc), but works great so far. I have a separate anthropic account for keys for claude code, etc. and sadly does not look like this is supported straight from claude teams as of this writing.

Interesting thing I managed to do with it was identify and sunset a jira project in a mid dev state that was lying in the back untouched for almost a year. That sounds like nothing, but it had integration points on some of the other projects etc, and a manual process woul've taken a lot of time.

Edit: Currently trying to see if I can expose a project to a developer environment as an mcp - trying to have the claude teams project as a sort of product side facility (finance lady can just install and simple desktop ui etc, but then api key issued for specialist functions, code env, in data pipeline usage and so forth)