forgejo-process-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORGEJO_URL | No | Forgejo base URL. | http://127.0.0.1:3310 |
| FORGEJO_TOKEN | Yes | Forgejo API token (required). | |
| FORGEJO_MCP_POLL_MS | No | Watcher poll interval in milliseconds. | 15000 |
| FORGEJO_MCP_STATE_DIR | No | Directory for events/watches state. | ~/.forgejo-process-mcp |
| FORGEJO_MCP_WEBHOOK_PORT | No | Webhook listener port (0 disables it). | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Forgejo delivery process: git ops, PRs, and ASYNC CI/CD. cicd_start returns immediately — continue development; poll cicd_events for failure/deploy notifications.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| repo_createC | Create a Forgejo repository |
| repo_listB | List repositories of the authenticated user |
| git_cloneC | Clone a repository into a local directory |
| git_branchC | Checkout or create a branch in a local repo |
| git_commitB | Stage all changes and commit in a local repo |
| git_pushC | Push the current (or given) branch to a remote |
| pr_openD | Open a pull request |
| pr_statusC | Get pull request state (mergeable, CI linkage) |
| pr_mergeC | Merge a pull request |
| ci_runsC | List recent Forgejo Actions runs for a repo |
| cicd_startA | Commit+push the working dir, register a CI/CD watch, and RETURN IMMEDIATELY. Do not block on the run — continue development; completion/failure arrives via cicd_events. |
| cicd_eventsB | Drain pending CI/CD events (failures, greens, deploy completions). Call between development steps. |
| watch_listC | List active CI/CD watches |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools target a distinct resource+action pair (repo_create vs git_clone vs pr_merge vs ci_runs), so an agent can generally pick correctly. The main overlap is cicd_start, which bundles commit+push+watch registration and thus collides partially with git_commit/git_push, and the trio ci_runs / cicd_events / watch_list requires reading descriptions to separate.
Two conventions coexist: resource-first names (pr_status, pr_open, repo_create, repo_list, ci_runs, watch_list) and verb-first names (git_clone, git_commit, git_push, cicd_start, cicd_events). Each family is internally readable, but the mix means `pr_open` and `git_clone` follow opposite orderings in the same set.
13 tools is well within the sweet spot for a dev-workflow server and each one maps to a real step (repo, branch, commit, push, PR, CI watch). Nothing appears redundant or padded at this count.
The local-git-to-PR-plus-CI loop is covered, but notable gaps remain: no pr_list or PR close/comment/review, no repo_get or repo_delete, and no file read/write or git status/diff to inspect state before committing. Agents can work around some of this, but read-side PR and repo inspection are dead ends.