Back to Browse

Progi MCP Server

by Zseta
Developer ToolsUse Caution0.4MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP-native workflow engine: teach agents your processes once, they execute them consistently.

About

MCP-native workflow engine: teach agents your processes once, they execute them consistently.

Security Report

0.4
Use Caution0.4Critical Risk

Valid MCP server (1 strong, 3 medium validity signals). 13 known CVEs in dependencies (1 critical, 5 high severity) Package registry verified. Imported from the Official MCP Registry.

5 files analyzed · 14 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

Unverified package source

We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.

What You'll Need

Set these up before or after installing:

Custom path for the Progi SQLite database fileOptional

Environment variable: PROGI_DB_PATH

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-zseta-progi": {
      "env": {
        "PROGI_DB_PATH": "your-progi-db-path-here"
      },
      "args": [
        "progi"
      ],
      "command": "uvx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

License: MIT PyPI MCP


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

ToolDescription
create_taskCreate a new task under a given workflow (status todo); returns a preview of its first step
list_tasksList tasks, optionally filtered by status and/or workflow
start_or_continue_taskMain work-loop entry point — starts or resumes a task and returns the current step's playbook, input data, and output spec
update_progress_notesOverwrite a task's progress notes (mid-step save point)
finish_stepMark the current step complete, store its output, and advance to the next step (or mark done)

Workflow authoring

ToolDescription
get_process_skeleton_promptReturn the Pass 1 system prompt for turning a plain-language description into a structured workflow skeleton
get_playbook_authoring_promptReturn the Pass 2 system prompt for authoring a step's playbook (injects workflow context)
save_workflowPersist a new workflow, its steps, and playbooks
list_workflowsReturn all workflows with their ordered steps

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

VariableDefaultPurpose
PROGI_DB_PATHOS data dir (platformdirs)SQLite file location
PROGI_WEB_HOST127.0.0.1Web UI bind host
PROGI_WEB_PORT8000Web UI port
PROGI_NO_WEB0Set to 1 to disable the web UI

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

Reviews

No reviews yet

Be the first to review this server!