Loading ToolBench

Reading the current corpus…

forgejo-mpc MCP server · F · ToolBench

← Browse

forgejo-mpc

github.com/MiggiV2/forgejo-mpc

MCP server for interacting with Forgejo (a self-hosted Git service) repositories, issues, pull requests, and releases

<=2025-11-25STREAMABLE_HTTP13 tools

48/100

Definition Quality51

Protocol Readiness69

Supportability28

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · evidence: Streamable HTTP

No deprecated protocol patterns detected

Summary

Server defines 13 tools with consistent naming (verb_noun pattern: forgejoCreate*, forgejoList*, forgejoGet*, forgejoUpdate*, forgejoMerge*). All tools have descriptions (10-50 chars, below ideal 50-200 baseline). Input schemas present with type declarations and parameter descriptions. However, descriptions are terse and lack context on WHEN to use each tool, prerequisites, or recovery guidance. No output schemas documented. No error handling guidance visible. Complex types like CreateRepoOption and CreateIssueOption are referenced but not expanded in source, making full schema validation impossible. Risk annotations (WRITE, READ_ONLY, IRREVERSIBLE) are present but not mapped to tool annotations in the MCP protocol.

Tools (13)

forgejoCreateIssuewriteauth50/100

Create an issue in a repository.

forgejoCreateOrgRepowriteauth50/100

Create a repository in an organization.

forgejoCreatePullRequestwriteauth50/100

Create a pull request in a repository.

forgejoCreateReleasewriteauth50/100

Create a release in a repository.

forgejoCreateUserRepowriteauth50/100

Create a repository for the authenticated user.

forgejoGetPullRequestread onlyauth50/100

Get a pull request by index.

forgejoGetReporead onlyauth50/100

Get a repository.

forgejoListActionTasksread onlyauth50/100

List a repository's action tasks.

Issues (5)

HIGHtool-description ↗

Descriptions are terse (10-50 chars) and lack context. 'Create a repository for the authenticated user' does not explain WHEN to use forgejoCreateUserRepo vs forgejoCreateOrgRepo, what happens on success, or what errors to expect. Baseline for A+ tools is 50-200 chars with WHAT/WHEN/PREREQUISITES.

forgejoCreateUserRepoforgejoCreateOrgRepoforgejoCreateIssueforgejoCreateReleaseforgejoCreatePullRequest

HIGHresponse-shaper ↗

Output schemas not documented. Tools return complex types (Repository, Release, Issue, PullRequest) but no schema is visible in source. LLMs cannot plan downstream calls or extract required fields (e.g., repo_id for chaining). Baseline: 100% of A+ tools document return types.

forgejoGetRepoforgejoListReleasesforgejoCreateReleaseforgejoListIssuesforgejoListPullRequests

HIGHrecovery-guide ↗

Recommendations

Expand all tool descriptions to 50-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and any prerequisites. Example: 'Create a repository in an organization. Use this when you have org permissions; use forgejoCreateUserRepo for personal repos. Returns repo_id for chaining to other tools.'
Document output schemas for all tools. For forgejoGetRepo, specify: returns {repo_id, name, owner, url, description, is_private, created_at}. For list tools, include pagination fields (total_count, page, limit) and cap results at 20-50 items.
Add error handling guidance to tool descriptions. Example: 'If the org does not exist, returns 404 with message. Try forgejoListOrgs() to find valid org names. If you lack permissions, returns 403, contact the org admin.'
Expand complex input types in schema definitions. For CreateRepoOption, inline the fields: {name (required, 1-255 chars), description (optional), private (optional, boolean), auto_init (optional, boolean)}. Use enums for constrained fields.
Map risk annotations to MCP tool annotations. Mark forgejoCreateUserRepo, forgejoCreateOrgRepo, forgejoCreateRelease, forgejoCreateIssue, forgejoCreatePullRequest with destructiveHint=true. Mark forgejoMergePullRequest with destructiveHint=true and idempotentHint=false (merging twice fails). Mark read-only tools with readOnlyHint=true.

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)

Score history

Overall score trend

First recorded score · v2 rubric

48/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	48	<=2025-11-25	v2