forgejo-mcp

Create repository

create_repository

Create a new Forgejo or Gitea repository for your account or an organization. Configure visibility, README initialization, description, and default branch.

Instructions

Create a repository for the authenticated user, or for an organization if org is given.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_repository"
  }
}

Input Schema

Name	Required	Description
`org`	No	Create under this organization instead of the user
`name`	Yes
`private`	No
`auto_init`	No	Initialize with a README
`description`	No
`default_branch`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

B3.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write/non-destructive profile is covered. The description adds the authentication context ('for the authenticated user'), which is legitimately new information, but says nothing about permissions needed for org creation or side effects such as initial commit creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the default behavior stated before the conditional override. Zero filler, though it is arguably too terse given the surrounding schema gaps.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation tool with no output schema and only one-third parameter documentation, the description leaves the agent without needed context: default visibility, what auto_init produces, default branch behavior, and what happens on name collision are all unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (org and auto_init documented). The description only restates the `org` parameter's effect, which the schema already explains, and gives no meaning to `name`, `private`, `description`, or `default_branch` — so it fails to compensate for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Create) and resource (repository) and even clarifies the owner resolution: authenticated user by default, organization when `org` is supplied. It does not explicitly distinguish itself from siblings like fork_repository or get_repository, but the creation semantics are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The `org` clause implies the selection condition (personal vs organizational repo), which is useful routing context. However, there is no guidance on when not to use it (e.g., to copy an existing repo use fork_repository) and no prerequisites such as org membership or name-uniqueness requirements.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server