Agentmako logo

Agentmako

by drhalto

Local-first codebase intelligence MCP server indexing code, schema, diagnostics, and findings with SQLite and optional Postgres support.

Install Agentmako

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "drhalto-agentmako": {
      "command": "npx",
      "args": [
        "-y",
        "agentmako"
      ],
      "env": {
        "AGENTMAKO_DB_PATH": "YOUR_VALUE_HERE",
        "AGENTMAKO_LOG_LEVEL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y agentmako

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

agentmako is a local-first codebase intelligence engine providing AI coding agents structured context packets, indexed code and schema facts, diagnostics, and review notes via MCP. It indexes your project into a local SQLite store and optionally supports Postgres/Supabase schema snapshots. Designed to help agents understand project structure, relevant files, routes, symbols, and diagnostics before editing, it reduces redundant discovery and raw grep usage. It runs entirely locally with no hosted service required.

Use cases

  • Index and query project codebase facts and diagnostics
  • Answer evidence-backed questions about project structure and database schema
  • Track and review diagnostics, linting, and code findings
  • Provide deterministic context packets for AI coding agents
  • Integrate with MCP clients to enhance coding agent workflows

Key features

  • Local SQLite-backed indexing of code, schema, and diagnostics
  • MCP server exposing tools like reef_ask, reef_status, reef_verify, and reef_impact
  • Support for Postgres/Supabase schema snapshots and read-only inspection
  • Hot-reloaded YAML rule packs for custom linting and cross-file rules
  • Integration with TypeScript, ESLint, Oxlint, Biome, and staged git diagnostics
  • Bundled Claude Code plugin for enhanced agent capabilities

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

20/20 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · agentmako (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars54Stargazers on the source repository.
npm downloads1.2kPackage downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

From the project README

agentmako logo

agentmako

npm version Smoke Tests License: Apache 2.0 Node.js >=20 agentmako MCP server

agentmako is a local-first codebase intelligence engine for AI coding tools.

It gives agents like Codex, Claude Code, Cursor, and local harnesses a compact Reef-first tool surface for understanding a project before they edit it. Mako indexes your repo, builds local SQLite-backed facts, tracks diagnostics and review notes, and answers evidence-backed questions instead of making the agent orchestrate broad tool chains or rediscover everything with raw grep.

Mako is built for the first mile of coding-agent work:

What files matter? What routes, symbols, tables, diagnostics, and prior findings are relevant? What should the agent read next?

What You Get

  • MCP server for coding agents: agentmako mcp
  • Local dashboard: agentmako dashboard
  • Primary project query: reef_ask across code, database, findings, diagnostics, instructions, freshness, and literal checks
  • Queryable workflow orientation: mako_help
  • Deterministic context expansion: context_packet
  • _hints on tool results so agents get result-specific next steps
  • Central MCP annotations so clients can distinguish safe reads, live reads, and local-state mutations
  • Compact loop/fallback tools: reef_status, reef_verify, reef_impact, live_text_search, lint_files, and tool_batch
  • Reef Engine facts and findings across indexed, working-tree, and staged state
  • Reef convention extraction for auth guards, runtime boundaries, generated paths, route patterns, and schema usage
  • TypeScript, ESLint, Oxlint, Biome, and staged git diagnostic ingestion
  • Hot-reloaded .mako/rules YAML rule packs, including primitive cross-file helper-bypass rules via canonicalHelper
  • Optional Postgres/Supabase schema snapshots and read-only DB inspection
  • Local DB review comments for notes on tables, RLS, triggers, publications, subscriptions, and replication
  • Recall, acknowledgements, and agent feedback for repeated review work

Everything important runs locally. No hosted service is required.

Install

Requires Node.js 20 or newer.

Terminal
npm install -g agentmako

Confirm the CLI is available:

bash
agentmako --version
agentmako doctor

You should see green checks for configuration and the local API service.

Prefer to build from source (e.g. to contribute)? See Develop From Source at the bottom of this file.

Happy Path Setup

1. Attach your real project

Go to the project you want Mako to understand:

bash
cd C:/path/to/your/project

Attach and index it:

bash
agentmako connect . --no-db

Use --no-db for the first run. It gets the code intelligence path working before adding database scope.

2. Confirm Mako sees the project

bash
agentmako status .
agentmako tool list

Run a real Reef query:

bash
agentmako --json tool call . reef_ask "{\"question\":\"where should I inspect auth route state?\"}"

If that returns an evidence-backed answer, facts, findings, or next queries, the core setup is working.

reef_ask plans over code, database, durable findings, diagnostics, and exact literal evidence. App-flow questions favor file, route, and finding evidence; RLS/schema questions favor database facts and review comments. To inspect project rules of thumb directly:

bash
agentmako --json tool call . project_conventions "{}"

3. Configure your MCP client

Add this to your MCP client config:

config.json
{
  "mcpServers": {
    "mako-ai": {
      "command": "agentmako",
      "args": ["mcp"]
    }
  }
}

Restart the MCP client and confirm the mako-ai server starts.

In the agent, default to reef_ask. The compact starting surface is:

  • reef_ask for project questions across code, database, findings, diagnostics, freshness, and quoted literal checks
  • reef_status for maintained issues, changed files, stale diagnostics, and watcher/schema health
  • reef_verify for the completion gate over diagnostic freshness and open loops
  • reef_impact for changed-file blast radius and convention risks
  • mako_help for an ordered workflow recipe with prefilled arguments
  • live_text_search for exact current-disk regex/glob inventories
  • lint_files for bounded diagnostics and .mako/rules findings
  • tool_batch for independent read-only follow-ups
  • tool_search to discover specialized route, graph, DB, finding, refresh, or context-expansion tools only when the compact surface points at a concrete need

4. Optional: use an agent plugin

Plain MCP works anywhere, but the bundled plugins add Mako-specific skills and include the same agentmako mcp wiring.

Prerequisites:

  • Claude Code installed
  • Node.js 20+ on PATH (the plugin runs npx -y agentmako mcp, which fetches the published agentmako package automatically — no separate global install required)
  • Your target project already attached with agentmako connect

Claude Code stable path:

Terminal
claude plugin validate .\mako-ai-claude-plugin
claude --plugin-dir .\mako-ai-claude-plugin

New generated plugin layouts:

Terminal
claude plugin validate ./plugins/claude-code
codex marketplace add ./plugins
ln -s "$(pwd)/plugins/cursor" ~/.cursor/plugins/local/mako-ai
gemini extensions install ./plugins/gemini

Inside the agent, confirm the mako-ai MCP server is connected.

The plugin exposes these skills:

  • /mako-ai:mako-guide
  • /mako-ai:mako-discovery
  • /mako-ai:mako-trace
  • /mako-ai:mako-neighborhoods
  • /mako-ai:mako-graph
  • /mako-ai:mako-database
  • /mako-ai:mako-code-intel
  • /mako-ai:mako-workflow

Use the plugin when you want Claude Code to load Mako-specific guidance for which tools to call and how to interpret their results.

5. Optional: launch the dashboard

From your target project:

bash
agentmako dashboard .

This starts the local API, harness service, and web dashboard.

6. Optional: add Supabase/Postgres awareness

Mako works without a database. Add this only after code intelligence is working.

For a one-time interactive setup:

bash
agentmako connect .

For CI or scripted setup using an environment variable:

bash
set DATABASE_URL=postgres://...
agentmako connect . --db-env DATABASE_URL --yes

Then refresh and verify the local schema snapshot:

bash
agentmako refresh .
agentmako verify .

Interactive mode stores database secrets in your OS keychain by default. Project config stores references, not plaintext DB URLs.

Normal Daily Loop

From the target project:

bash
agentmako status .
agentmako dashboard .
agentmako --json tool call . context_packet "{\"query\":\"fix the broken auth callback route\"}"

For staged review checks:

bash
agentmako git precommit . --json

For database review notes:

bash
agentmako --json tool call . db_review_comment "{\"objectType\":\"replication\",\"objectName\":\"supabase_database_replication\",\"category\":\"review\",\"comment\":\"Check publication coverage before relying on realtime events.\",\"tags\":[\"supabase\",\"replication\"]}"

Develop From Source

If you want to hack on Mako itself, clone and build instead of installing from npm.

Prerequisites:

  • Node.js 20 or newer
  • Git
  • Corepack (corepack enable, included with modern Node.js)
bash
git clone https://github.com/drhalto/agentmako.git
cd agentmako
corepack pnpm install
corepack pnpm run build
npm link ./apps/cli

npm link ./apps/cli makes the source-built CLI available as agentmako on your PATH, replacing any global npm install. Re-run corepack pnpm run build after pulling changes.

To go back to the published version: npm install -g agentmako.

Development Checks

bash
corepack pnpm run typecheck
corepack pnpm run build
corepack pnpm run test:smoke:reef-tooling
corepack pnpm run test:smoke:reef-model-facing-views

Full verification:

bash
corepack pnpm test

Repository Layout

text
apps/
  cli/              agentmako CLI and MCP entrypoint (the published package)
  web/              local dashboard
packages/
  contracts/        public TypeScript contracts and tool schemas
  config/           shared config helpers
  logger/           shared logger
  sdk/              programmatic SDK
  store/            SQLite stores, migrations, and query helpers
  tools/            shared tool implementations
  harness-core/     local agent harness runtime
  harness-tools/    action tools available to the harness
  harness-contracts/ harness contracts and provider catalog
services/
  api/              local API and MCP transports
  engine/           Reef Engine fact/finding pipeline
  harness/          local harness HTTP service
  indexer/          repo and schema indexing logic
  worker/           background worker
extensions/         provider and integration packages
storage/            schema migrations, models, queries
test/smoke/         smoke coverage
mako-ai-claude-plugin/ Claude Code plugin with Mako skills

More Docs

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Agentmako

To provide AI coding agents with structured, indexed context and diagnostics about a codebase locally, reducing redundant discovery.

No, all indexing and query operations run locally without any hosted backend.

It supports optional Postgres and Supabase schema snapshots and read-only inspection.

Configure the MCP client to run the command `agentmako mcp` as a server and use tools like `reef_ask` for queries.

Node.js version 20 or newer is required.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAgentmako AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/drhalto-agentmako?style=directory)](https://allmcps.com/mcp/drhalto-agentmako)
HTML Embed
<a href="https://allmcps.com/mcp/drhalto-agentmako"><img src="https://allmcps.com/api/badge/drhalto-agentmako?style=directory" alt="Agentmako on AllMCPs" /></a>