Skip to main content
Glama
amonstack

gitea-mcp

by amonstack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

configure_gitea

Configure Gitea connection at runtime: set base URL, owner, repo, or username to trigger credential re-discovery from local sources. Use to switch instances or identities mid-session.

Instructions

Configure the Gitea connection at runtime (session-scoped, never persisted). Accepts base_url, owner, repo, and/or username — at least one is required. Providing base_url or username triggers credential re-discovery from the existing four sources (GITEA_REPO_URL repo URL, git config [gitea] token, GITEA_TOKEN env, git credential helpers). Tokens never pass through this tool; they are always read from the local credential sources. username strictly narrows the git credential lookup to that identity (no fallback to other identities). Use this when the server started unconfigured or when you need to switch instances/identities mid-session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNoDefault repository name for tool calls that omit the repo argument.
ownerNoDefault repository owner for tool calls that omit the owner argument.
base_urlNoGitea instance base URL (e.g. https://gitea.example.com). Providing base_url — even unchanged — triggers credential re-discovery for that host. Use this as the 'I just added a git credential, refresh now' idiom.
usernameNoSelects which identity git's credential machinery should use for the host. The lookup is narrowed to this username — no fallback to other identities. Providing username triggers credential re-discovery.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • changedInput schema / properties / base_url / description
      Previous value: -"Gitea instance base URL (e.g. https://gitea.example.com). Providing base_url — even unchanged — triggers credential re-discovery for that host. Use this as the 'I just added a credential-store entry, refresh now' idiom."New value: +"Gitea instance base URL (e.g. https://gitea.example.com). Providing base_url — even unchanged — triggers credential re-discovery for that host. Use this as the 'I just added a git credential, refresh now' idiom."
    • changedInput schema / properties / username / description
      Previous value: -"Selects which identity to use from the git credential store. Host-matching entries are strictly filtered by this username — no fallback to other identities. Providing username triggers credential re-discovery."New value: +"Selects which identity git's credential machinery should use for the host. The lookup is narrowed to this username — no fallback to other identities. Providing username triggers credential re-discovery."
  2. Addedv0.5.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden and handles it well: session-scoped and never persisted, token-free invocation, credential re-discovery triggers, and strict username narrowing with no fallback are all explicitly stated.

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

Conciseness5/5

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

Three dense sentences with no filler. The core purpose and scope are front-loaded, followed by credential behavior and explicit usage guidance. Every sentence contributes necessary information.

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

Completeness4/5

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

The description covers scope, parameter semantics, trigger conditions, credential sources, and usage timing, which is sufficient for correct invocation. It does not describe the success/error response shape, but with no output schema and a simple configuration purpose this is a minor gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real value beyond the schema: base_url triggers re-discovery even when unchanged, username strictly scopes identity lookup, and at least one parameter is required despite the schema listing zero required fields.

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

Purpose5/5

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

States a specific verb and resource ('Configure the Gitea connection'), clarifies runtime scope and persistence behavior, and lists accepted inputs. No sibling tool performs this configuration role, so the description clearly distinguishes it.

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

Usage Guidelines4/5

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

Explicitly says when to use the tool: 'when the server started unconfigured or when you need to switch instances/identities mid-session.' It does not name exclusions or alternatives, but the context is unambiguous given the unique configuration purpose.

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

Deploy Server

Other Tools