MCP.so
登录

Progi MCP Server

@zseta

基本信息

分类

其他

传输方式

stdio

作者

zseta

提交者

Attila Tóth

关于 Progi MCP Server

MCP-native workflow engine for your AI harness. 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.

Progi MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

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

Progi MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

点击上方按钮,在临时沙箱中运行此服务器并实时获取工具列表。

概览

What is Progi?

Progi is an MCP-native workflow engine that teaches your AI agent your preferred processes. It stores structured workflows with per-step playbooks in a local SQLite database, survives context resets, and provides a monitoring web UI. It is intended for developers who want their agent to follow consistent, reusable procedures across sessions.

How to use Progi?

Describe your workflow in plain language to Progi. It runs a two-pass authoring process to create a structured skeleton and per-step playbooks, then persists everything with save_workflow. Run tasks with create_task, then start_or_continue_task to step through the workflow, and submit_output to advance. Monitor progress via the web UI (default at 127.0.0.1:8000) or disable it with PROGI_NO_WEB=1. Configure database path using the PROGI_DB_PATH environment variable.

Key features of Progi

  • Structured workflows with per-step playbooks
  • Two-pass authoring from plain-language descriptions
  • Persistent storage in a local SQLite database
  • Live monitoring web UI for task progress
  • Step advancement with output submission
  • Playbook updating without re-authoring the entire workflow

Use cases of Progi

  • Automating a PR review workflow: create an integration, review code, publish PRs
  • Standardizing a recurring maintenance routine across sessions
  • Onboarding new team members by codifying team processes
  • Running a multi-step data pipeline with human-in-the-loop checkpoints
  • Iteratively improving a workflow by tweaking playbooks between runs

常见问题

1

What is Progi and how does it differ from basic prompt‑based workflows?

Progi stores workflows as structured steps with playbooks in a persistent database. Unlike plain prompts, these workflows survive context resets, and each future task automatically picks up the latest playbook changes.

2

How do I configure the database location and the web UI?

Set the `PROGI_DB_PATH` environment variable to an absolute path (defaults to the OS data directory). The web UI binds to `127.0.0.1:8000` by default; you can change the port with `PROGI_WEB_PORT` or disable it entirely with `PROGI_NO_WEB=1`.

3

Where does Progi store workflow and task data?

All data is stored in a local SQLite database whose location is controlled by `PROGI_DB_PATH`. No external cloud or server is required.

4

What transpors does Progi use for communication?

Progi exposes an MCP‑compliant tool interface over stdio (when invoked via the `uvx` command) plus a web UI for monitoring. It does not provide its own network transport or authentication layer beyond the MCP protocol.

5

What are the two authoring passes?

Pass 1 converts a plain-language description into a structured workflow skeleton using `get_process_skeleton_prompt`. Pass 2 authors each step’s detailed playbook using `get_playbook_authoring_prompt`. The result is persisted with `save_workflow`.

评论

其他 分类下的更多 MCP 服务器