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.
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?
Choose Tickiti when
- You need dedicated capabilities in the Support & Service Management domain.
- You want tools like
create_ticket, respond_to_ticket, close_ticket.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 45/100 · Fair | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | JIRA_URLJIRA_USERNAMEJIRA_API_TOKENJIRA_PERSONAL_TOKENCONFLUENCE_URLCONFLUENCE_USERNAMECONFLUENCE_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6,035 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 33 | Not listed |
| Full listing | View Tickiti | View MCP Atlassian |
Tools & capabilities
Tickiti tools 33
create_ticketOpen a ticket (subject+content, template, or intervention), with assignee, priority, status and participants; `is_public` is requiredrespond_to_ticketPost a response; change status, hold, assignee, priority, queue, subject, participants; `send_full_email` for the whole reply by emailclose_ticketClose, optionally with a final reply and a resolutionedit_responseChange a response in place (whole body, find/replace, visibility) with no notification — or publish an internal note and notifydelete_responseSoft-delete a responseadd_participantsChange participantsdelete_ticketsDelete tickets (by number, or everything from one sender) and undo itmerge_ticketsMerge two tickets (the older survives)link_ticketsThe Linked panelmove_responsesRepair a thread: move or copy responses, or split them off into a new linked ticketchange_originatorChange who raised a ticketdelete_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": {
"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"
}
}
}
}