publish-pilot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| preflightA | Check tools (git, gh, registry CLI), logins and git identity. Run first. |
| install_toolA | Install a tool with winget, brew or apt. |
| check_namesB | Check a package name on its registry and a repo name on your GitHub. If taken, returns the first free alternative (npm: @user/name first). |
| loginA | Start a browser login. Returns a job with the URL and code; the user signs in and approves. Poll job_status until running is false. |
| job_statusC | Status and output of a login/publish job; without id, lists jobs. |
| scaffold_projectA | Create a project: source, test, README, LICENSE, CHANGELOG, .gitignore, manifest (0.1.0). With repoUrl, also CI and release workflows. Never overwrites files. |
| add_workflowsB | Write ci.yml and release.yml (on v* tags: test, publish via OIDC unless the version exists, GitHub release from CHANGELOG). Keeps existing files unless overwrite. |
| run_checksB | Secret scan, install, lint, typecheck, build, test (npm scripts, .venv + pytest, or cargo). Stops at the first failure. |
| inspect_packageB | Publish dry run: files that would ship, junk/secret warnings, registry check. |
| git_commitA | Stage all and commit (git init -b main if needed). Refuses if secrets would be committed. |
| create_github_repoB | Create the GitHub repo from the folder and push. If it is already this folder's origin, just pushes. |
| publish_packageB | Publish to the registry; returns a job (npm approval opens in a terminal). Skips existing versions, and refuses for 24 h after an E429. |
| setup_trusted_publishingB | Link the package to release.yml for OIDC publishing. npm: npm trust (package must exist; user approves 2FA). PyPI/crates: opens the settings page with the values; user clicks Save. |
| tag_and_releaseA | Tag v, push branch and tag together, and create the GitHub release from CHANGELOG unless release.yml does. Never moves tags. |
| watch_workflowC | Result of the workflow run for HEAD (default release.yml), with failed logs. |
| bump_versionA | Bump the version and add notes to CHANGELOG (no notes: Unreleased becomes the version). Does not commit. |
| verify_installA | In a fresh temp folder, install the published package (or clone repoUrl) and run commands in order, stopping at the first failure. Its executables are on PATH. |
| notifyB | Desktop notification, e.g. 'Ready for your approval'. url opens a github.com, npmjs.com, pypi.org or crates.io page. |
| run_commandA | Run a shell command (PowerShell on Windows, sh elsewhere). Destructive ones (force-push, deleting tags/repos/releases, unpublish, rm -r) are refused. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| publish_project | Step-by-step plan to take a project from nothing to a published GitHub repo and/or package using these tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Most tools target distinct phases of the publishing workflow (preflight, scaffold, checks, publish, release, verify), and the descriptions clarify boundaries. Some overlap remains between run_checks, inspect_package, and verify_install, and run_command is a broad escape hatch that could be used for many tasks.
The set is consistently snake_case, but the naming pattern is mixed: most tools are action_noun, while others are bare verbs/nouns (preflight, login, notify, job_status) or noun_verb (git_commit). The names are readable, but not predictably uniform.
19 tools is slightly heavy for a typical MCP server but justified by the broad publish-and-release lifecycle. Each tool maps to a meaningful step, though the surface could be consolidated by merging related check/verify operations.
The surface covers the full publishing lifecycle: setup, scaffolding, validation, versioning, repo creation, CI/release workflows, publishing, trusted publishing, tagging, verification, and a safe command runner. No major dead ends are apparent for the stated purpose.