MCP Tomticket vs MCP Atlassian

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

MCP Tomticket logoMCP TomticketSupport & Service Management · Local subprocess (stdio)TomTicket helpdesk MCP: tickets, replies, time, customers, chats, and KB51GoodAuth: 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.49FairAuth: api key required

Verdict: choose MCP Tomticket for support & service management work as a local process; 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?

MCP Tomticket logoChoose MCP Tomticket when

  • You need dedicated capabilities in the Support & Service Management domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like tomticket_list_open_tickets, tomticket_list_tickets, tomticket_get_ticket.
Explore MCP Tomticket

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.

SpecMCP Tomticket logoMCP TomticketMCP Atlassian logoMCP Atlassian
CategorySupport & Service ManagementSupport & Service Management
Quality signal51/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)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 4 views 0 installs 0 upvotes
Tools9Not listed

Tools & capabilities

MCP Tomticket tools 9

  • tomticket_list_open_ticketsChamados abertos
  • tomticket_list_ticketsTodos, com filtros
  • tomticket_get_ticketDetalhe + respostas + horários
  • tomticket_reply_ticketResposta do atendente (`start_date`/`end_date` lançam horário)
  • tomticket_comment_ticketComentário interno
  • tomticket_finish_ticketFinaliza (`time_work` em minutos)
  • tomticket_start_statusCronômetro de status
  • tomticket_create_ticketAbre chamado
  • tomticket_transfer_ticketTransferir / vincular atendente

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.

MCP Tomticket

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-tomticket": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-tomticket"
      ]
    }
  }
}

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

MCP Tomticket is categorized under Support & Service Management and uses a local stdio subprocess. MCP Atlassian belongs to Support & Service Management and uses a local stdio subprocess. Pick MCP Tomticket 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.

MCP Tomticket 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 mcp-tomticket and sooperset-mcp-atlassian as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Tomticket has a quality signal of 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars. MCP Atlassian has 49/100 (Fair) with 4 views, 0 installs and 6,035 GitHub stars.