Ext Ops Panel
Open dashboard
Comparison

Atlassian vs MCP Task Orchestrator

Atlassian is an MCP server published by sooperset. Marketplaces we read that list it: 1 (Docker MCP Catalog). MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-15. 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

Where each is published
MarketplaceAtlassianMCP Task Orchestrator
Docker MCP Catalog Listed
Version: sha256:ecec36c62279
Forks (GitHub): 1 395
Pulls (Docker Hub): 166 264
Stars (Docker Hub): 22
Stars (GitHub): 6 001
Not marked · First seen
Listed
Version: sha256:eab0bb62611a
Forks (GitHub): 24
Stars (GitHub): 207
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 3.16.0
Forks (GitHub): 24
Stars (GitHub): 207
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

Atlassian vs MCP Task Orchestrator
FactAtlassianMCP Task Orchestrator
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)6 001 (better)207 (worse)
Pulls (Docker Hub) (differs)166 264No figure on Docker Hub
Forks (GitHub) (differs)1 395 (better)24 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/atlassian)On your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0)
Transportstdiostdio
Tools it declares (differs)8042
Environment variables it asks for (differs)8, secrets among them: 47, secrets among them: 0
LicenceMITMIT
Repository (differs)github.com/sooperset/mcp-atlassiangithub.com/jpicklyk/task-orchestrator
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

In its own words, on Docker MCP Catalog:

Tools for Atlassian products (Confluence and Jira). This integration supports both Atlassian Cloud and Jira Server/Data Center deployments.

MCP Task Orchestrator

In its own words, on Official MCP Registry:

Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates

How to run each

Atlassian As a local MCP server: Docker image

Claude Code
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/atlassian

Requires: CONFLUENCE_API_TOKEN (secret), CONFLUENCE_PERSONAL_TOKEN (secret), JIRA_API_TOKEN (secret), JIRA_PERSONAL_TOKEN (secret)

MCP Task Orchestrator As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio task-orchestrator -- docker run -i --rm -v mcp-task-data:/app/data ghcr.io/jpicklyk/task-orchestrator:3.16.0

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Only Atlassian declares

  • confluence_add_comment
  • confluence_add_inline_comment
  • confluence_add_label
  • confluence_create_page
  • confluence_delete_attachment
  • confluence_delete_page
  • confluence_download_attachment
  • confluence_download_content_attachments
  • confluence_get_attachments
  • confluence_get_comments
  • confluence_get_inline_comments
  • confluence_get_labels
Show the remaining 68
  • confluence_get_page
  • confluence_get_page_children
  • confluence_get_page_diff
  • confluence_get_page_history
  • confluence_get_page_images
  • confluence_get_page_views
  • confluence_get_space_page_tree
  • confluence_move_page
  • confluence_reply_to_comment
  • confluence_search
  • confluence_search_user
  • confluence_update_page
  • confluence_update_page_section
  • confluence_upload_attachment
  • confluence_upload_attachments
  • jira_add_comment
  • jira_add_issues_to_sprint
  • jira_add_watcher
  • jira_add_worklog
  • jira_assign_issue
  • jira_batch_create_issues
  • jira_batch_create_versions
  • jira_batch_get_changelogs
  • jira_create_issue
  • jira_create_issue_link
  • jira_create_remote_issue_link
  • jira_create_sprint
  • jira_create_version
  • jira_delete_issue
  • jira_download_attachments
  • jira_edit_comment
  • jira_get_agile_boards
  • jira_get_all_projects
  • jira_get_board_issues
  • jira_get_field_options
  • jira_get_issue
  • jira_get_issue_dates
  • jira_get_issue_development_info
  • jira_get_issue_images
  • jira_get_issue_proforma_forms
  • jira_get_issue_sla
  • jira_get_issue_watchers
  • jira_get_issues_development_info
  • jira_get_link_types
  • jira_get_proforma_form_details
  • jira_get_project_components
  • jira_get_project_fields
  • jira_get_project_issues
  • jira_get_project_versions
  • jira_get_queue_issues
  • jira_get_service_desk_for_project
  • jira_get_service_desk_queues
  • jira_get_sprint_issues
  • jira_get_sprints_from_board
  • jira_get_transitions
  • jira_get_user_profile
  • jira_get_worklog
  • jira_link_to_epic
  • jira_remove_issue_link
  • jira_remove_watcher
  • jira_search
  • jira_search_assignable_users
  • jira_search_fields
  • jira_transition_issue
  • jira_update_issue
  • jira_update_proforma_form_answers
  • jira_update_sprint
  • jira_update_version

Only MCP Task Orchestrator declares

  • add_section
  • add_template_section
  • apply_template
  • bulk_create_sections
  • bulk_delete_sections
  • bulk_update_sections
  • bulk_update_tasks
  • create_dependency
  • create_feature
  • create_project
  • create_task
  • create_template
Show the remaining 30
  • delete_dependency
  • delete_feature
  • delete_project
  • delete_section
  • delete_task
  • delete_template
  • disable_template
  • enable_template
  • feature_to_markdown
  • get_feature
  • get_overview
  • get_project
  • get_sections
  • get_task
  • get_task_dependencies
  • get_template
  • list_templates
  • project_to_markdown
  • reorder_sections
  • search_features
  • search_projects
  • search_tasks
  • task_to_markdown
  • update_feature
  • update_project
  • update_section
  • update_section_metadata
  • update_section_text
  • update_task
  • update_template_metadata

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Atlassian asks for

  • CONFLUENCE_API_TOKEN (secret)
  • CONFLUENCE_PERSONAL_TOKEN (secret)
  • CONFLUENCE_URL
  • CONFLUENCE_USERNAME
  • JIRA_API_TOKEN (secret)
  • JIRA_PERSONAL_TOKEN (secret)
  • JIRA_URL
  • JIRA_USERNAME

Only MCP Task Orchestrator asks for

  • AGENT_CONFIG_DIR
  • DATABASE_PATH
  • LOG_FILE
  • LOG_LEVEL
  • MCP_HTTP_PORT
  • MCP_TRANSPORT
  • USE_FLYWAY

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Atlassian · What it can do: MCP Task Orchestrator · 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.

Where the data comes from: how the catalog is built