MCP.so
登录
M

Memtrace MCP Server

@syncable-dev

基本信息

分类

其他

传输方式

stdio

作者

syncable-dev

提交者

Lishuai Jing

关于 Memtrace MCP Server

Memtrace — Structural Memory for AI Coding Agents

#memory#code-intelligence#knowledge-graph#ast#structural-analysis#codebase-context#agent-memory#blast-radius#temporal-memory#bi-temporal#hybrid-search#graph-rag#developer-tools-ai-agents

Memtrace MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "memtrace": {
      "command": "memtrace",
      "args": [
        "mcp"
      ],
      "env": {
        "MEMTRACE_ARCADEDB_BOLT_URL": "bolt://localhost:7687"
      }
    }
  }
}

Memtrace MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Memtrace?

Memtrace is a structural memory layer for AI coding agents, delivered as an MCP server. It compiles any codebase into a live, bi-temporal knowledge graph from the AST, enabling agents like Claude Code, Cursor, Windsurf, and Zed to instantly query callers, callees, blast radius, dependency chains, and code evolution without re-reading source files on every turn.

How to use Memtrace?

Install Memtrace with a single command (npm install -g memtrace), start the graph server (memtrace start), and index your repository (memtrace index .). The MCP server starts automatically and connects to any MCP-compatible agent. No configuration, cloud account, or telemetry required.

Key features of Memtrace

  • Structural knowledge graph compiled from the AST across 12 languages and 3 IaC formats.
  • Bi-temporal episodic memory enables time-travel through code history beyond git commits.
  • Blast radius analysis computes exactly which files, functions, and services break before any change.
  • Hybrid retrieval engine fused BM25, HNSW vector search, and graph traversal.
  • Six traversal strategies: Impact, Novel, Recent, Compound, Directional, and Overview.
  • API topology mapping for cross-service dependency chains and dead endpoint detection.
  • 40+ MCP tools covering indexing, search, relationships, impact analysis, and graph algorithms.
  • Local-first, closed-source Rust—code never leaves the machine, no account, no telemetry.

Use cases of Memtrace

  • Giving AI coding agents persistent structural memory to reduce token waste by up to 90%.
  • Computing blast radius before a refactor—knowing exactly which callers, services, and tests break.
  • Detecting structural drift and regressions mid-session, catching breaking changes the moment they happen.
  • Onboarding agents to large, unfamiliar codebases instantly with full symbol graph and dependency tree queryable from the first turn.
  • Time-travelling through code evolution to understand how a function, type, or module changed over time.

常见问题

1

What agents and IDEs does Memtrace work with?

Memtrace works with any MCP-compatible agent or IDE, including Claude Code, Cursor, Zed, VS Code, Windsurf, Continue, Aider, and OpenAI Codex CLI.

2

Does Memtrace send my code to the cloud?

No. Memtrace is fully local-first. Your code never leaves your machine. There is no account, no telemetry, and no cloud dependency.

3

How long does indexing take?

Initial indexing typically completes in seconds for most repositories. Each file save triggers an incremental re-index that completes in 200–800ms.

4

Which programming languages are supported?

Memtrace supports 12 programming languages and 3 IaC formats via Tree-sitter grammars: TypeScript, JavaScript, Python, Rust, Go, Java, C, C++, Ruby, PHP, C#, Swift, plus Terraform, Kubernetes, and Docker.

5

How is Memtrace different from RAG-based code search tools?

RAG tools return lexically or semantically similar snippets. Memtrace returns structurally meaningful answers—the actual callers, real blast radius, and deterministic dependency chains—because it reasons over a compiled knowledge graph, not over embeddings.

6

Does Memtrace replace existing tools like LSP or GitHub Copilot?

No. Memtrace is additive. It gives agents a structural memory layer that LSP servers and embedding-based tools don't provide. Existing tools keep working; agents gain access to 40+ additional MCP tools for graph-based reasoning.

评论

其他 分类下的更多 MCP 服务器