All servers / Productivity / Pecot Workflow MCP server
Pecot Workflow MCP server
pecot-workflow MCP server (standalone distribution)
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-18 on package version 9.0.0. Package: @pecot/workflow-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 16 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.3 seconds including download)
- Tools offered: 39
- Last published: 2026-11-18
- Weekly downloads (npm): 6,891
- License: MIT · Direct dependencies: 4
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
project_list0 of 1 parameter describedList available projects
project_search2 of 3 parameters describedSearch projects through the GitHub API
project_init5 of 6 parameters describedAdd pecot-workflow fields to an existing project, and add the Blocked and Needs Attention options to the fields that already exist
project_create5 of 6 parameters describedCreate a new project (to add the fields to an existing project, use project init)
project_activate4 of 5 parameters describedActivate an initialized project
project_link8 of 8 parameters describedAdd or update a repository in the project config
project_get1 of 2 parameters describedShow the value of a key of the project config (aggregation_repo: the Epic aggregation repository)
project_set4 of 5 parameters describedSet a key of the project config (aggregation_repo: the Epic aggregation repository)
project_unset2 of 3 parameters describedClear a key of the project config; without aggregation_repo, creating an Epic needs --repo
board_show2 of 2 parameters describedShow the dashboard of the project board
board_add4 of 5 parameters describedAdd an Issue to the project board with a GraphQL mutation (for an Issue created outside pecot)
board_move4 of 5 parameters describedUpdate the status of an Issue on the project board by Issue number (pecot commands normally set the status themselves)
board_sync2 of 3 parameters describedMove the Issues in Ready, Blocked, Active and In Review to the columns and Status values their judgment calls for, and delete the Archived items beyond the latest 20 from the board
issue_create17 of 17 parameters describedCreate Issues from Markdown files with frontmatter
issue_show4 of 5 parameters describedFetch Issue details efficiently (GraphQL, only the needed fields)
issue_comment7 of 8 parameters describedPost a comment on an Issue
issue_block6 of 7 parameters describedAdd a blocked-by (prerequisite) to an Issue, or change the wait kind and reason of an existing one
issue_unblock4 of 5 parameters describedRemove a blocked-by (prerequisite) from an Issue
issue_reopen5 of 6 parameters describedReopen a closed Issue (also sets the status on the board)
session_start6 of 7 parameters describedCreate a branch linked to an Issue (shown in the Development section of the Issue)
session_show2 of 3 parameters describedShow the branch, repository and work Issue of the session
session_finish5 of 6 parameters describedClean up after a merged PR (close related Issues, delete branches, local cleanup)
pr_create13 of 13 parameters describedCreate a PR (pull request)
pr_show4 of 5 parameters describedGet PR details efficiently (GraphQL, only the needed fields)
pr_check2 of 3 parameters describedShow all the information to check before creating a PR
pr_merge3 of 4 parameters describedMerge a PR with the asynchronous merge API (a PR in a stack must be the bottom one)
pr_restack5 of 6 parameters describedRestack the current branch onto the new position of its base branch
review_finish11 of 12 parameters describedFinish an automated review: post a comment on the PR only when the review stopped (failed, limit or setup-missing)
release_check3 of 4 parameters describedRun the pre-release checks; for an nx repository only the alerts are checked
release_create4 of 5 parameters describedCreate a GitHub release and its tag (the release notes come from the CHANGELOG)
release_merge5 of 6 parameters describedMerge a release PR with a regular merge
tracker_sync3 of 4 parameters describedRewrite the open Tracker's list for a source: Dependabot PRs waiting for a human decision, or open security alerts
worktree_add9 of 10 parameters describedCreate a new worktree
worktree_remove5 of 6 parameters describedRemove a worktree
worktree_init2 of 3 parameters describedCreate the worktree config files in the main worktree
worktree_link4 of 5 parameters describedApply or update symlinks in existing worktrees
branch_delete4 of 4 parameters describedDelete a remote branch (a protected branch is never deleted)
workflow_install5 of 6 parameters describedWrite a GitHub Actions workflow template of pecot into the repository
workflow_doctor2 of 3 parameters describedCheck that the repository has the workflow file and the settings it needs
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.