Atlassian vs Tiflux
Atlassian is an MCP server published by sooperset. Marketplaces we read that list it: 1 (Docker MCP Catalog). Tiflux is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Atlassian |  Tiflux |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ecec36c62279 Forks (GitHub): 1 411 Pulls (Docker Hub): 168 496 Stars (Docker Hub): 22 Stars (GitHub): 6 023 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 (last published figure) Stars (GitHub): 0 (last published figure) Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Atlassian | Tiflux |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 023 | 0 (last published figure) |
| Pulls (Docker Hub) (differs) | 168 496 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 411 | 0 (last published figure) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/atlassian) | Remote server (api.mcp.ai/p_tiflux) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 80 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 4 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/sooperset/mcp-atlassian | github.com/mcp-dir/tiflux-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Atlassian
Tools for Atlassian products (Confluence and Jira). This integration supports both Atlassian Cloud and Jira Server/Data Center deployments.
Tiflux
Wrapper for the official Tiflux API v2 (help desk and service desk): tickets with replies to the req
How to run each
Atlassian As a local MCP server: Docker image
claude mcp add --env "CONFLUENCE_API_TOKEN=<YOUR_CONFLUENCE_API_TOKEN>" --env "CONFLUENCE_PERSONAL_TOKEN=<YOUR_CONFLUENCE_PERSONAL_TOKEN>" --env "JIRA_API_TOKEN=<YOUR_JIRA_API_TOKEN>" --env "JIRA_PERSONAL_TOKEN=<YOUR_JIRA_PERSONAL_TOKEN>" --transport stdio atlassian -- docker run -i --rm -e CONFLUENCE_API_TOKEN -e CONFLUENCE_PERSONAL_TOKEN -e JIRA_API_TOKEN -e JIRA_PERSONAL_TOKEN mcp/atlassianRequires: CONFLUENCE_API_TOKEN (secret), CONFLUENCE_PERSONAL_TOKEN (secret), JIRA_API_TOKEN (secret), JIRA_PERSONAL_TOKEN (secret)
Tiflux As a remote MCP server
claude mcp add --transport http tiflux-mcp https://api.mcp.ai/p_tifluxCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Tiflux has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Tiflux publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Tiflux publish no settings it asks for, so we do not compare settings.
What it can do: Atlassian · What it can do: Tiflux · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.