Codebase Memory MCP vs Tickiti

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

Codebase Memory MCP logoCodebase Memory MCPKnowledge & Memory · Local subprocess (stdio)Code-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcp73GreatAuth: no auth requiredTickiti logoTickitiSupport & Service ManagementConnect AI assistants to the Tickiti helpdesk API: tickets, queries, reports and admin.45FairAuth: not declared

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

Which MCP server should you choose?

Codebase Memory MCP logoChoose Codebase Memory MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like index_repository, search_graph, query_graph.
Explore Codebase Memory MCP

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCodebase Memory MCP logoCodebase Memory MCPTickiti logoTickiti
CategoryKnowledge & MemorySupport & Service Management
Quality signal73/100 · Great45/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars47,3520
Directory activity 9 views 1 installs 1 upvotes 1 views 0 installs 0 upvotes
Tools1733

Tools & capabilities

Codebase Memory MCP tools 17

  • index_repositoryIndex a repository. full/moderate add semantics; fast omits them; cross-repo-intelligence links services. Reports coverage gaps.
  • search_graphFind symbols via BM25 query, regex name/qn filters, or semantic_query. Rows keep qn/file/lines and in/out over CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS.
  • query_graphRead-only Cypher for multi-hop, aggregation, complexity, or cross-service analysis. Default: 200 visible rows with exact/lower-bound totals and truncation; continue safely with next_cursor. graph=missed is a file tree of flagged coverage gaps; absence is not proof of completeness. Use get_graph_schema(diagnostics=full) for properties.
  • trace_pathTrace callers/callees, data flow, or cross-service paths. Defaults exclude tests and resolver evidence. Rows keep qn/hop with explicit totals, relations, and continuations.
  • get_code_snippetRead a search_graph symbol. auto bounds source and outlines large containers; full restores up to 500 lines. Source/outline pages continue; coverage_note marks gaps.
  • get_file_outlineDeclaration outline of one exact repository-relative file: optional exact label filter, source order, exact total/offset/limit paging; file/folder/container nodes excluded.
  • get_graph_schemaGet node-label and edge-type counts. diagnostics=full also lists queryable properties.
  • compare_graphsCompare two indexed snapshots: deterministic target-only additions and base-only removals of stable node/edge identities; each set capped by limit and a 512 KiB budget with exact totals and truncation reasons.
  • get_architectureCompact counts, languages, packages, entry points. Request structure, dependencies, routes, hotspots, boundaries, layers, clusters, cycles, or file_tree; path scopes a directory.
  • search_codeGraph-ranked text search: compact symbols, full bounded source, or file paths.
  • list_projectsList projects with stable paging. Identity is lean; stats adds graph sizes.
  • delete_projectDelete a project from the index
  • +5 more on the listing page

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

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.

Codebase Memory MCP

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

Tickiti

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

Frequently asked questions

Codebase Memory MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. Tickiti belongs to Support & Service Management and uses an install path we have not confirmed yet. Pick Codebase Memory MCP for knowledge & memory work and Tickiti 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.

Codebase Memory MCP is listed as free. Auth: no auth required. Tickiti has no declared pricing — check the project's own site. 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 deusdata-codebase-memory-mcp and tickiti as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Codebase Memory MCP has a quality signal of 73/100 (Great) with 9 views, 1 installs and 47,352 GitHub stars. Tickiti has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.