Tickiti vs Git
A side-by-side look at the Tickiti and Git 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 Git for version control 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 Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Version Control |
| Quality signal | 45/100 · Fair | 81/100 · Excellent |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,526 |
| Directory activity | 1 views 0 installs 0 upvotes | 51 views 0 installs 0 upvotes |
| Tools | 33 | 16 |
| Full listing | View Tickiti | View Git |
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
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on 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.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
Tickiti is categorized under Support & Service Management and uses an install path we have not confirmed yet. Git belongs to Version Control and uses a local stdio subprocess. Pick Tickiti for support & service management work and Git for version control.
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. Git is listed as free. Auth: no auth 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 git 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. Git has 81/100 (Excellent) with 51 views, 0 installs and 91,526 GitHub stars.