MCP-memento

mcp
Guvenlik Denetimi
Basarisiz
Health Gecti
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 10 GitHub stars
Code Basarisiz
  • rm -rf — Recursive force deletion command in .github/workflows/move-server-latest.yml
  • process.env — Environment variable access in vscode-extension/src/extension.js
Permissions Gecti
  • Permissions — No dangerous permissions requested

Bu listing icin henuz AI raporu yok.

SUMMARY

Local-first MCP server that gives AI agents durable repo memory and fast semantic code context.

README.md

memento-mcp

Server Release
Latest Binary Tag
VS Code Extension Release
Go Version
License: MIT

Support on Ko-fi

A local-first MCP server that gives AI agents durable, high-signal memory for your repository: indexed code context, semantic relationships, fast search, and explicit notes that persist across sessions.

fun easy tl;dr version of the change logs: Nomit Memento

Languages

Documentation

What It Does

  • Exposes MCP tools for repo operations: repo_list_files, repo_read_file, repo_search, repo_related_files, repo_context, repo_switch_workspace
  • Maintains an on-disk code index per repository for fast, bounded context retrieval
  • Stores explicit repo-scoped notes: memory_upsert, memory_search, memory_clear
  • Supports a companion VS Code extension that installs and configures the server

How It Works

  1. The server starts over stdio JSON-RPC and registers MCP tools.
  2. It builds and updates a local chunk index under ~/.memento-mcp/.
  3. Change detection is incremental:
    • Default (auto): filesystem watcher first, fallback to git status polling for git repos if watcher fails
    • Configurable via MEMENTO_CHANGE_DETECTOR (auto / fs / git)
  4. Context tools combine:
    • Indexed chunks and scoring
    • Language-aware relationships (Go, TS/JS, PHP)
    • Hard byte and line limits for LLM context safety
  5. Explicit notes are stored separately as durable, repo-scoped memory.

Project Structure

  • cmd/server/ - entrypoint
  • internal/mcp/ - MCP server and tool handlers
  • internal/indexing/ - chunking, manifest, search, incremental indexing
  • internal/app/ - app lifecycle wiring
  • vscode-extension/ - companion extension (installer and MCP config UX)
  • docs/ - usage docs and ADRs

Contributing

Prerequisites

  • Go 1.25.5
  • Node.js (only if working on vscode-extension/)

Local Development

git clone https://github.com/caiowilson/MCP-memento.git
cd MCP-memento
make build
./bin/memento-mcp

Generic Client Onboarding

./bin/memento-mcp print-config
./bin/memento-mcp print-guidance

Run Tests

go test ./...

VS Code Extension Development

cd vscode-extension
npm install
npm run build

Contribution Flow

  1. Create a branch from main.
  2. Make focused changes with tests and docs updates.
  3. Run go test ./... (and extension build/tests when applicable).
  4. Open a PR with:
    • Problem statement
    • Approach
    • Validation steps
    • Any tool or behavior changes

Roadmap Themes

  • Better context quality and ranking
  • Broader semantic language support
  • Extension UX and install reliability
  • Release automation and operational tooling

Yorumlar (0)

Sonuc bulunamadi