Gitea MCP integration for AI agents.
Connect AI agents to Gitea through 93 structured actions, including check pull request merged, add collaborator, delete branch, and clear issue labels. Revie…
- ACTION CONTRACTS
- 93
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Gitea integration exposes
The Gitea Agent App exposes 93 provider-backed actions for developer tools work. Its current contract lets an authorized agent check whether a gitea pull request has been merged, add a collaborator to a gitea repository, and delete a branch of a gitea repository. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Gitea account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Gitea capabilities.
Showing 12 of 93 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_pull_request_mergedREADCheck whether a Gitea pull request has been merged.
INPUTS: owner / repo / pullRequestNumber
add_collaboratorWRITEAdd a collaborator to a Gitea repository.
INPUTS: owner / repo / collaborator / permission
delete_branchHIGH IMPACTDelete a branch of a Gitea repository.
INPUTS: owner / repo / branch
clear_issue_labelsREVIEWRemove all labels from a Gitea issue.
INPUTS: owner / repo / issueNumber
add_issue_labelsWRITEAdd labels to a Gitea issue.
INPUTS: owner / repo / issueNumber / labels
create_branchWRITECreate a new branch in a Gitea repository.
INPUTS: owner / repo / newBranchName / oldRefName
create_commit_statusREADCreate a commit status for a commit SHA in a Gitea repository.
INPUTS: owner / repo / sha / state / context
create_fileWRITECreate a file in a Gitea repository.
INPUTS: owner / repo / filePath / content / message
create_issueWRITECreate an issue in a Gitea repository.
INPUTS: owner / repo / title / body / assignees
create_issue_commentWRITECreate a comment on a Gitea issue.
INPUTS: owner / repo / issueNumber / body
create_labelWRITECreate a label in a Gitea repository.
INPUTS: owner / repo / name / color / description
create_milestoneWRITECreate a milestone in a Gitea repository.
INPUTS: owner / repo / title / description / state
INPUT CONTRACTS
Know what the action needs before it runs.
check_pull_request_merged
ownerREQUIRED- Owner of the repository.
repoREQUIRED- Name of the repository.
pullRequestNumberREQUIRED- Pull request number within the repository.
add_collaborator
ownerREQUIRED- Owner of the repository.
repoREQUIRED- Name of the repository.
collaboratorREQUIRED- Username of the collaborator to add.
permissionOPTIONAL- Permission level of the collaborator.
delete_branch
ownerREQUIRED- Owner of the repository.
repoREQUIRED- Name of the repository.
branchREQUIRED- Name of the branch to delete.
clear_issue_labels
ownerREQUIRED- Owner of the repository.
repoREQUIRED- Name of the repository.
issueNumberREQUIRED- Issue number within the repository.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check Pull Request Merged
Check whether a Gitea pull request has been merged. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_pull_request_mergedControl Add Collaborator
Add a collaborator to a Gitea repository. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_collaboratorVerify with Create Commit Status
Create a commit status for a commit SHA in a Gitea repository. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_commit_statusSAFETY BOUNDARY
Operate Gitea with explicit limits
- Authorize Gitea with API key and grant only the provider access required by the selected actions.
- 41 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_branch`, `delete_file`, and `delete_issue_comment` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Gitea rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Gitea task completed successfully.
CONNECTION MODEL
API key
Gitea personal access token. Create it in User Settings > Applications > Manage Access Tokens on your Gitea instance, as documented at https://docs.gitea.com/development/api-usage
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 44
- WRITE SIGNALS
- 27
- HIGH IMPACT
- 14
- REVIEW SIGNALS
- 8
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Gitea.