Jira and Confluence through your MCP server

Connect Jira and Confluence through your organisation's MCP server when a technical user isn't allowed: one flow, a sign-in with your own account, and clear rules for what kanman may see.

Some organisations don’t hand out a technical user for Jira or Confluence. The only allowed way in is their own MCP server. kanman can use that server as the way in. Teams then work with Jira and Confluence as usual: kanman reads issues, sprints, releases, comments and pages, and notices changes.

Connect

  1. Open Workspace settings › Connections › Jira (or Confluence) and choose Connect.
  2. Under How does kanman get in? choose Through an MCP server.
  3. Enter the server’s address from your IT, or pick a server that is already connected here.
  4. Choose how kanman signs in. Usually that’s As a person: you sign in with your own account in a small window.
  5. kanman checks the server and shows what it can do through it (see below).
  6. If the server also gives access to Confluence (or Jira), kanman offers to connect it too, with the same sign-in.
  7. Choose What kanman may see and save.

If the server only answers inside your company network, kanman reaches it through your runner. The sign-in then also runs there.

What kanman can do through the server

After the check you see a list of everything kanman does with Jira or Confluence:

  • A tick: works through this server.
  • Arrows: works, but the server sends no notifications, so kanman checks for changes every few minutes.
  • Not available: with one sentence why, for example “This server only reads, so on this connection I can’t comment in Jira.”

Through MCP servers kanman only reads for now. It doesn’t create, change or comment on anything.

kanman uses only servers it knows. If it doesn’t recognise the server as Jira or Confluence, it says so and doesn’t guess.

What kanman may see

When someone signs in with their own account, kanman could see everything that person sees. That’s why these rules always apply:

  • Nothing until you choose. kanman sees no project and no space until an admin picks them.
  • Jira: only the projects you pick. Issues with a security level are left out. You can also leave out issue types (for example Risk), labels and components, and add a JQL condition every issue must match.
  • Confluence: only the spaces you pick, and only pages without a view restriction, on the page itself or on a parent page.
  • Per team: each team sees only its own projects or spaces, within these rules.

Whatever falls outside these rules never reaches kanman’s models, a team or storage. When something is left out, kanman says so without naming it. The privacy overview counts how many items were left out, never what they were.

When something changes

  • The server’s tools change: kanman pauses the connection and the row says so. Choose Review to see what changed and approve it again.
  • The sign-in runs out: kanman asks the person who signed in, once, in their next update. Until then it says that Jira or Confluence isn’t available. Sign in again from the connection.
  • The server refuses kanman’s callback address: kanman shows the exact address. Give it to your IT so they can allow it.

Last updated: January 1, 0001

Open kanman