Github
Wire GitHub repos, releases, users, and workflow actions into your agent so shipping and repo chores stay in the chat.
Overview
com.mcparmory/github is a Build-phase MCP server that lets your agent manage GitHub repositories, users, releases, and workflow automation.
What is this MCP server?
- Manage repositories, users, and releases from agent-driven prompts
- Trigger and inspect GitHub Actions workflows without context-switching to the web UI
- Version 1.0.6 with stdio via uvx (mcparmory-github) or Docker ghcr.io/mcparmory/github:1.0.6
- Fits ship-phase release tagging and grow-phase changelog hygiene when chained after local commits
- Developer-tool MCP server—not a markdown skill; requires GitHub token and MCP registration
- Server version 1.0.6
- 2 packages (PyPI mcparmory-github and OCI ghcr.io/mcparmory/github:1.0.6)
- stdio transport
Community signal: 25 GitHub stars.
What problem does it solve?
You lose flow when every release, repo setting, or Actions check forces you out of the agent into github.com.
Who is it for?
Indie devs who ship from GitHub and want the agent to handle repos, releases, and Actions alongside coding tasks.
Skip if: Teams on GitLab-only or offline workflows with no GitHub org or token policy.
What do I get? / Deliverables
GitHub admin and release steps become tool calls your agent can plan and execute with your credentials.
- Agent-executed GitHub repo, user, release, and workflow operations with API-backed results
- Documented release and automation steps the agent can repeat in later ship iterations
Recommended MCP Servers
Journey fit
Most solo builders live in GitHub while they implement features, cut releases, and tune automation—placement on the build shelf reflects day-to-day repo operations from the agent. Integrations is the right subphase because this MCP is the bridge between your coding agent and GitHub’s HTTP APIs, not your local git binary alone.
How it compares
GitHub REST automation via MCP, not a local git skill or a hosted CI YAML generator by itself.
Common Questions / FAQ
Who is com.mcparmory/github for?
Solo builders and small teams on GitHub who want their coding agent to manage repos, releases, and workflows through MCP tools.
When should I use com.mcparmory/github?
Use it during build and ship when you need the agent to inspect or change GitHub resources—repos, releases, users, or Actions—without manual UI steps.
How do I add com.mcparmory/github to my agent?
Add a stdio MCP entry pointing to uvx mcparmory-github 1.0.6 or ghcr.io/mcparmory/github:1.0.6, supply a GitHub personal access token or app auth per your setup, and reload the agent’s MCP server list.