ingest_traces

MCP tool from Codebase Memory MCP by DeusData

Ingest runtime traces to validate HTTPCALLS edges.

How to use it

ingest_traces is exposed by the Codebase Memory MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the ingest_traces tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

FULL CODEBASE MEMORY MCP LISTING

Other tools in Codebase Memory MCP (13)

delete_project

Remove a project and all its graph data.

detect_changes

Map git diff to affected symbols + blast radius with risk classification.

get_architecture

Codebase overview: languages, packages, routes, hotspots, clusters, ADR.

get_code_snippet

Read source code for a function by qualified name.

get_graph_schema

Node/edge counts, relationship patterns, property definitions per label. Run this first.

index_repository

Index a repository into the graph. Auto-sync keeps it fresh after that.

index_status

Check indexing status of a project.

list_projects

List all indexed projects with node/edge counts.

manage_adr

CRUD for Architecture Decision Records. Query modes do not wait behind a same-project reindex; writes remain serialized.

query_graph

Execute Cypher-like graph queries (read-only).

search_code

Grep-like text search within indexed project files.

search_graph

Structured search by label, name pattern, file pattern, degree filters. Pagination via limit/offset.

trace_path

BFS traversal — who calls a function and what it calls (alias: tracecallpath). Depth 1-5.