Home / MCP registry index / Topics / Jira and Confluence
Jira and Confluence MCP servers, with their tools checked
Every server in the official MCP registry that mentions Jira and Confluence, with a public endpoint, read the way an MCP client reads it and checked for tool poisoning. The list updates as the registry does, and each server is read again every week.
8 listed. We have read the tools of 2 so far; the others want credentials first, could not be reached, or are still waiting for their first read.
These servers act inside an account you own, usually with a token you give them. Prefer the narrowest access the tools need, and check which tools can send, post or delete.
| Confluence io.github.pipeworx-io/confluence | 47 tools, nothing matched 2026-10-22 |
| Ichimoku Signal io.github.Fizzl13/ichimoku-signal | 8 tools, nothing matched 2026-10-22 |
| ai.waystation/jira ai.waystation/jira | not reachable 2026-10-22 |
| Atlassian Rovo MCP Server com.atlassian/atlassian-mcp-server | not read yet |
| Jira io.github.pipeworx-io/jira | not read yet |
| Statuspage io.github.pipeworx-io/statuspage | not read yet |
| Jira Key Shape io.github.sadri-dridi/jira-key-shape | not read yet |
| Commentify one.commentify/commentify | not read yet |
Choosing one
Open a server's page to see the tools it advertises, whether it sets instructions for the model, and our latest read. Here, 2 of the servers shown matched none of our tool-poisoning rules on their last read. A clean read means our rules found nothing, not that a server is harmless; still check what access it asks for. To check one that is not listed, paste its URL into the free MCP server check.
Related: GitHub · GitLab · Notion · Slack · Discord · Email · Calendar · Google Workspace · all topics