Tickiti vs MCP Atlassian

A side-by-side look at the Tickiti and MCP Atlassian MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Tickiti logoTickitiSupport & Service ManagementConnect AI assistants to the Tickiti helpdesk API: tickets, queries, reports and admin.45FairAuth: not declaredMCP Atlassian logoMCP AtlassianSupport & Service Management · Local subprocess (stdio)MCP server for Atlassian products (Confluence and Jira). Supports Confluence Cloud, Jira Cloud, and Jira Server/Data Center. Provides comprehensive tools for searching, reading, creating, and managing content across Atlassian workspaces.48FairAuth: api key required

Verdict: choose Tickiti for support & service management work; choose MCP Atlassian for support & service management as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Tickiti logoChoose Tickiti when

  • You need dedicated capabilities in the Support & Service Management domain.
  • You want tools like create_ticket, respond_to_ticket, close_ticket.
Explore Tickiti

MCP Atlassian logoChoose MCP Atlassian when

  • You need dedicated capabilities in the Support & Service Management domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN, JIRA_PERSONAL_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN.
Explore MCP Atlassian

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTickiti logoTickitiMCP Atlassian logoMCP Atlassian
CategorySupport & Service ManagementSupport & Service Management
Quality signal45/100 · Fair48/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredBYOK (pay the provider)
Required env varsNone listedJIRA_URLJIRA_USERNAMEJIRA_API_TOKENJIRA_PERSONAL_TOKENCONFLUENCE_URLCONFLUENCE_USERNAMECONFLUENCE_API_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars06,035
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools33Not listed

Tools & capabilities

Tickiti tools 33

  • create_ticketOpen a ticket (subject+content, template, or intervention), with assignee, priority, status and participants; `is_public` is required
  • respond_to_ticketPost a response; change status, hold, assignee, priority, queue, subject, participants; `send_full_email` for the whole reply by email
  • close_ticketClose, optionally with a final reply and a resolution
  • edit_responseChange a response in place (whole body, find/replace, visibility) with no notification — or publish an internal note and notify
  • delete_responseSoft-delete a response
  • add_participantsChange participants
  • delete_ticketsDelete tickets (by number, or everything from one sender) and undo it
  • merge_ticketsMerge two tickets (the older survives)
  • link_ticketsThe Linked panel
  • move_responsesRepair a thread: move or copy responses, or split them off into a new linked ticket
  • change_originatorChange who raised a ticket
  • delete_attachmentRemove one attachment (a malicious file, say), keeping a record of it
  • +21 more on the listing page

MCP Atlassian tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Tickiti

No confirmed install command for Tickiti yet — follow the setup steps linked from its listing page rather than a guessed package name.

MCP Atlassian

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "sooperset-mcp-atlassian": {
      "command": "uvx",
      "args": [
        "mcp-atlassian"
      ],
      "env": {
        "JIRA_URL": "YOUR_JIRA_URL_HERE",
        "JIRA_USERNAME": "YOUR_JIRA_USERNAME_HERE",
        "JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN_HERE",
        "JIRA_PERSONAL_TOKEN": "YOUR_JIRA_PERSONAL_TOKEN_HERE",
        "CONFLUENCE_URL": "YOUR_CONFLUENCE_URL_HERE",
        "CONFLUENCE_USERNAME": "YOUR_CONFLUENCE_USERNAME_HERE",
        "CONFLUENCE_API_TOKEN": "YOUR_CONFLUENCE_API_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

Tickiti is categorized under Support & Service Management and uses an install path we have not confirmed yet. MCP Atlassian belongs to Support & Service Management and uses a local stdio subprocess. Pick Tickiti for support & service management work and MCP Atlassian for support & service management.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Tickiti has no confirmed install command yet — follow its own setup instructions.

Tickiti has no declared pricing — check the project's own site. MCP Atlassian is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add tickiti and sooperset-mcp-atlassian as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Tickiti has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. MCP Atlassian has 48/100 (Fair) with 3 views, 0 installs and 6,035 GitHub stars.