Gitea
Manage Gitea repositories, issues, pull requests, releases and files.
About
Gitea ships in the w6w first-party pack. It declares 26 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.gitea- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Version Control · Developer Tools · DevOps & Infrastructure
Overview
Gitea is a self-hosted Git service, and this app puts the daily loop of running one — repositories, issues, pull requests, files and releases — behind a workflow, whichever instance an organisation happens to run.
Issue and pull request management is the core of it: open issues with labels attached, edit and comment on them, and open and merge pull requests, with the same care a person would take — an unfiltered issue listing defaults to issues alone rather than Gitea’s own mixed view that quietly includes every open pull request too. File actions read and write a repository’s contents directly, handling the underlying concurrency check automatically so a workflow doesn’t have to fetch a blob’s current state by hand before every edit. Releases and tags round it out, including finding the newest published release rather than an unpublished draft that happens to sort first.
Deleting a repository is here as well, deliberately made harder to trigger by accident than everything else, because unlike a bad commit it isn’t something a local clone can undo. Administrative surfaces — mirrors, packages, wikis, webhooks and Gitea’s own CI — stay out of scope in favor of the actions a workflow touches day to day.
Build with Gitea
Three routes to the same 26 actions. The Workflow tab is generated from Gitea's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create or update a file
file-write Commit a file's contents, fetching the sha so a concurrent change is not lost.
Comment on an issue or pull request
issue-comment-create Post a comment. Works on pull requests too — they are issues in Gitea's model.
Get the latest release
release-get-latest The newest published release, skipping drafts and prereleases.
Delete a repository
repo-delete Permanently delete a repository, its issues, pull requests and releases.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Gitea's real ids.
{
"manifestVersion": "2",
"name": "gitea-example",
"steps": [
{
"id": "branch-list",
"uses": {
"app": "io.w6w.gitea",
"action": "branch-list",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"repo": "<repo>"
}
}
]
}Here are some of the things you can do
-
List branches
readbranch-list -
List commits
readcommit-list -
Get a file
readfile-get -
Create or update a file
performfile-write -
Comment on an issue or pull request
performissue-comment-create
+21 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Gitea, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Gitea. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "branch-list",
payload: {
repo: "<value>",
// owner: "<value>",
// returnAll: "<value>",
// limit: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action branch-list --payload '{"repo":"<value>"}'Give an AI agent Gitea — without giving it Gitea's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.gitea#branch-list",
"input": {
"repo": "<repo>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Gitea connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Gitea's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Gitea itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Gitea declares its own checks, so its health is a property of the app rather than something the host guesses at.
Gitea instance reachable
This connection's own server, via its unauthenticated /api/v1/version endpoint. Sends no credential — an expired token must not make the server look down.