@mempalace/mcp-dev
Provides tools for retrieving branch context (current branch, SHA, recent commits), changed files, and git diffs within a repository.
Enables running Jest tests directly from the MCP client, returning pass/fail counts and structured failure details.
Allows running TypeScript type checking (tsc --noEmit) in a service directory, returning structured errors with file, line, column, and code.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@mempalace/mcp-devSearch my codebase for payment processing functions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@mempalace/mcp-dev
An MCP (Model Context Protocol) server that gives AI coding assistants grounded, branch-scoped context about your codebase. It provides semantic code search via MemPalace, git change tracking, a persistent change ledger, TypeScript/Jest dev lifecycle tools, and a built-in Project Tracks (Conductor) methodology for structured feature work.
Features
Feature | Description |
Semantic code search | Natural-language queries over your indexed codebase via MemPalace embeddings |
Branch context | Current branch, SHA, recent commits — always oriented |
Change ledger | Append-only JSONL log of every AI-assisted change with full provenance |
Dev lifecycle | Run |
Git diff | Full or file-scoped diff output |
Project Tracks | Create and manage markdown-based feature tracks (plan/spec/index/metadata) |
Prerequisites
Node.js ≥ 18
Python ≥ 3.9 with MemPalace installed
A git repository to point at
Install MemPalace
pip install mempalace
# or from the fork with exclude-patterns support:
pip install git+https://github.com/2loch-ness6/mempalace@feat/exclude-patterns-configQuick Start
1. Install the MCP server
npm install -g @mempalace/mcp-devOr use without installing via npx:
npx @mempalace/mcp-dev2. Configure environment variables
export MCP_REPO_DIR=/path/to/your/repo # defaults to process.cwd()
export MCP_PALACE_DIR=~/.mempalace/active # MemPalace data directory
export MCP_PALACE_WING=code # wing name (namespace) for your repo
export MEMPALACE_PYTHON=python3 # python binary with mempalace installed3. Index your codebase
mempalace --palace ~/.mempalace/active mine /path/to/your/repo --wing code --mode projects4. Add to your MCP client config
For Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"mempalace-mcp-dev": {
"command": "npx",
"args": ["@mempalace/mcp-dev"],
"env": {
"MCP_REPO_DIR": "/path/to/your/repo",
"MCP_PALACE_DIR": "/home/you/.mempalace/active",
"MCP_PALACE_WING": "code",
"MEMPALACE_PYTHON": "python3"
}
}
}
}Environment Variables
Variable | Default | Description |
|
| Absolute path to your git repository root |
|
| MemPalace data directory |
|
| Wing (namespace) name within the palace |
|
| Path to the change ledger file |
|
| Directory containing project track folders |
|
| Python binary (must have |
MCP Tools Reference
Code Search
Tool | Description |
| Semantic search over indexed codebase. Accepts |
| Re-index files changed since the last git commit. Call after editing to keep search current |
Branch & Git
Tool | Description |
| Returns current branch, SHA, short SHA, and last 5 commit messages |
| Files changed vs |
| Full diff output. Optional |
Change Ledger
Tool | Description |
| Append an entry to the ledger (files affected, description, reason, tags, optional track link) |
| Read recent ledger entries. Optional |
Dev Lifecycle
Tool | Description |
| Run |
| Run Jest in a service directory. Returns pass/fail counts and structured failure details |
Project Tracks (Conductor)
Tool | Description |
| List all live tracks (directories containing |
| Read |
| Overwrite |
| Read |
| Overwrite |
| Read |
| Overwrite |
| Scaffold a new track directory with all four files |
Project Tracks Methodology (Conductor)
Project Tracks is a lightweight, file-based feature management system. Each track is a directory containing up to four files:
conductor/tracks/
└── my-feature-20260501/
├── plan.md ← living task list; the status source of truth
├── spec.md ← technical spec, design decisions, acceptance criteria
├── index.md ← short summary and linked resources
└── metadata.json ← machine-readable metadata (id, owner, status, dates)Rules:
A directory is a live track only if it contains
plan.md.plan.mdis always read/written live from disk (never via MemPalace — no staleness).Track slugs must match
[a-zA-Z0-9][a-zA-Z0-9_-]*(max 100 chars).
Bootstrapping tracks in a new project:
# Create the tracks directory
mkdir -p conductor/tracks
# Use the MCP tool to scaffold a track
# (or copy from templates/track/ in this package)Template files are included in templates/track/ for manual scaffolding.
MemPalace Configuration (mempalace.yaml)
Place a mempalace.yaml at the root of MCP_REPO_DIR to control how files are indexed. A generic example is provided in mempalace.yaml.example.
Key sections:
wing— must matchMCP_PALACE_WINGexclude_patterns— gitignore-syntax patterns to skip during miningrooms— semantic routing rules (keyword → room name) for search scoping
Development
git clone https://github.com/your-org/mempalace-mcp-dev
cd mempalace-mcp-dev
npm install
npm run build
npm testSee CONTRIBUTING.md for contribution guidelines.
License
MIT — see LICENSE.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/2loch-ness6/mempalace-mcp-dev'
If you have feedback or need assistance with the MCP directory API, please join our Discord server