Memory Pickle MCP Server

Local CLI that turns a coding goal into ranked, token-budgeted repository context for AI agents.

Local serverstdioGo

What is the Memory Pickle MCP MCP server?

Memory pickle mcp mcp server lets Claude, Cursor and other MCP clients work with Memory Pickle MCP directly. Local CLI that turns a coding goal into ranked, token-budgeted repository context for AI agents.

What Memory Pickle MCP does

Local CLI that turns a coding goal into ranked, token-budgeted repository context for AI agents.

Tools it exposes

Once connected, the assistant can call these 9 tools directly:

  • init — Bootstrap .codesmell/ config and cache
  • doctor — Check local readiness
  • map — Repo structure, languages, public symbols
  • search — Ranked evidence for a query
  • pack — Budgeted context pack for a coding goal
  • explain — Deep-dive a file or symbol
  • diff — Changed files, symbols, risk hints
  • test-plan — Focused test suggestions
  • review — Deterministic findings with evidence

Installing the memory pickle mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Memory Pickle MCP sits in that group, and the shape of its toolset — init, doctor, map among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • With 9 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Memory Pickle MCP.
  • Maintained by Justar96, written in Go.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the memory pickle mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
initBootstrap .codesmell/ config and cache
doctorCheck local readiness
mapRepo structure, languages, public symbols
searchRanked evidence for a query
packBudgeted context pack for a coding goal
explainDeep-dive a file or symbol
diffChanged files, symbols, risk hints
test-planFocused test suggestions
reviewDeterministic findings with evidence

Example prompts to try

  • Use Memory Pickle MCP to init.
  • Use Memory Pickle MCP to doctor.
  • Use Memory Pickle MCP to map.

Frequently asked questions

It connects Memory Pickle MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (init, doctor, map, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Memory Pickle MCP directly.