maki

Run a dev command, save its terminal output per project, and let MCP-capable agents read the logs without copy/paste.

maki --name dev pnpm dev

Then ask your agent:

Check the maki dev logs and fix the error.

How it works

maki --name dev pnpm dev
  ├─ runs pnpm dev
  ├─ prints output to your terminal
  └─ writes logs to .maki/runs/<run-id>.log

maki-mcp --project /path/to/project
  └─ exposes MCP tools that read .maki logs

Each run gets:

.maki/
  active.json
  runs/
    20260710-090000-a1b2c3.log
    20260710-090000-a1b2c3.json

The run id is timestamp + random suffix. --name is the human label agents can use, like dev, api, web, or worker.

Install

Recommended:

pipx install maki-mcp

or:

uv tool install maki-mcp

On Windows without pipx:

py -m pip install --user pipx
py -m pipx ensurepath
pipx install maki-mcp

Avoid system-wide pip install maki-mcp. Some Python installs, like Homebrew Python, block it with an "externally managed environment" error. pipx/uv tool install maki as a CLI without touching system Python.

Maki works in any project, not just Python projects:

cd my-node-app
maki --name dev pnpm dev

The package is maki-mcp, but the commands are:

maki
maki-mcp

Usage

Start your app through maki:

maki --name dev pnpm dev
maki --name api npm run api
maki --name worker python worker.py

If you omit --name, it defaults to dev:

maki pnpm dev

Start the MCP server for that project:

maki-mcp --project /path/to/project

MCP tools:

• list_runs()
• latest_logs(name="dev", lines=200)
• get_log(run_id="...", lines=200)

MCP config

Use stdio transport. No port needed.

Claude Code

CLI:

claude mcp add maki -- maki-mcp --project /path/to/project

Config shape:

{
  "mcpServers": {
    "maki": {
      "command": "maki-mcp",
      "args": ["--project", "/path/to/project"]
    }
  }
}

Codex

~/.codex/config.toml:

[mcp_servers.maki]
command = "maki-mcp"
args = ["--project", "/path/to/project"]

Or with the CLI:

codex mcp add maki -- maki-mcp --project /path/to/project

Antigravity / agy

~/.gemini/config/mcp_config.json:

{
  "mcpServers": {
    "maki": {
      "command": "maki-mcp",
      "args": ["--project", "/path/to/project"]
    }
  }
}

Pi

Pi does not ship built-in MCP support, so maki ships a Pi package that registers equivalent Pi tools.

Install from GitHub:

pi install git:github.com/mr-jones123/maki

Or test from a local checkout:

pi -e /path/to/maki

Pi tools exposed:

• maki_list_runs()
• maki_latest_logs(name="dev", lines=200)
• maki_get_log(run_id="...", lines=200)

Ask:

Use maki_latest_logs for dev and inspect the error.

Publishing

Use Conventional Commits:

fix: patch release
feat: minor release
feat!: major release

Merges to main are versioned by Python Semantic Release and published to PyPI by GitHub Actions.