Progi - MCP-native Workflow Engine

Progi teaches your agent how you like to get things done. So you can do your best work without re-explaining your process or losing context between sessions.

Get started

Add Progi to your MCP client config (GH Copilot / Cursor / Claude Code / etc):

{
  "mcpServers": {
    "progi": {
      "command": "uvx",
      "args": ["progi"]
    }
  }
}

Progi Monitoring starts automatically at `http://127.0.0.1:8000`.

If you want to start Monitoring on a different port:

{
  "mcpServers": {
    "progi": {
      "command": "uvx",
      "args": ["progi"],
      "env": {
        "PROGI_WEB_PORT": "8080"
      }
    }
  }
}

How it works

1. Describe your workflow

*"Hey Progi, help me create workflow for creating integrations, reviewing code, and publishing PRs."*

Describe your process in plain language. You can be detailed or just provide a rough idea. Progi stores it as a structured workflow with per-step playbooks.

2. Run tasks, stay in the loop

*"Hey Progi, start a new task, we need to review a new docs PR in the repo."*

Your agent loads the workflow, works through each step using your playbooks, and loops you in at critical checkpoints to review output.

3. Monitor progress

Progi Monitoring gives you a live view of every running and completed task — status, progress, and the full output history across all your workflows.

4. Optimize as you go

Tweak playbooks in Progi Monitoring between runs. Because workflows live in a database and survive context resets, every future task picks up your changes automatically — your process gets sharper with each iteration.

MCP Tools

Work loop

Workflow authoring

Authoring is two passes: Pass 1 turns a plain-language description into a structured skeleton; Pass 2 authors each step's playbook. `save_workflow` persists both.

Configuration

Run modes: `uvx progi` (MCP + web UI), `uvx progi --no-web` (MCP only), `uvx progi-web` (web UI only).

> Use an absolute path for `PROGI_DB_PATH`