ClawLink

How to connect Gitea to OpenClaw

Connect Gitea to OpenClaw with ClawLink: paste your Gitea key once and 47 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Gitea
Gitea
GiteaAPI KEYMCP

Community managed lightweight code hosting solution written in Go.. Once connected, OpenClaw can read and act on Gitea from chat — pairing, token refresh, and tool wiring handled for you.

47 tools

The usual route to Gitea access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Gitea setup: install one ClawHub skill, connect Gitea in the browser, and OpenClaw can call real Gitea actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect OpenClaw to Gitea.

  1. 1

    Install the plugin

    Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:

    openclaw plugins install clawhub:clawlink-plugin
  2. 2

    Connect Gitea

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Gitea?"

Install by command

The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:

openclaw plugins install clawhub:clawlink-plugin

Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Gitea in the ClawLink dashboard — paste your Gitea API key once.

Verify the connection by asking OpenClaw:

Use Gitea to activitypub person and walk me through the result in plain English.

Using a different agent?

The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Gitea is connected in the dashboard, that agent calls the same 47 Gitea tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Gitea MCP for OpenClaw

Looking for a Gitea MCP server for OpenClaw? ClawLink connects Gitea to OpenClaw and exposes 47 Gitea tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Gitea integration works the same way.

What the OpenClaw Gitea integration can do

47 Gitea tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 47.

30 of 47 Gitea tools for OpenClaw

ToolWhat it does
Activitypub person gitea_activitypub_personRetrieve the ActivityPub Person actor for a Gitea user
Get branch gitea_get_branchRetrieve a repository branch, its commit, and effective protection state
Get commit gitea_get_commitRetrieve one repository commit by Git ref or SHA
Get commit status gitea_get_commit_statusGet the combined status and individual checks for a commit reference
Get current user gitea_get_current_userReturn the Gitea user authenticated by the connected API token
Get general API settings gitea_get_general_api_settingsRetrieve the Gitea instance's global API settings, including pagination limits and response
Get general attachment settings gitea_get_general_attachment_settingsRetrieve the Gitea instance's global settings for file attachments including enabled status
Get general repository settings gitea_get_general_repository_settingsRetrieve the Gitea instance's global settings for repositories including feature flags for
Get general ui settings gitea_get_general_ui_settingsRetrieve the Gitea instance's global settings for UI including default theme, allowed
Get git object gitea_get_git_objectRetrieve a repository Git tree or blob by object SHA
Get gitignore template info gitea_get_gitignore_template_infoRetrieve information about a specific gitignore template
Get label template info gitea_get_label_template_infoRetrieve all labels from a specific label template
Get license template info gitea_get_license_template_infoRetrieve information about a specific license template
Get node info gitea_get_node_infoRetrieve the nodeinfo of the Gitea application
Get pull request gitea_get_pull_requestRetrieve one pull request and its current merge state and references
Get release by tag gitea_get_release_by_tagRetrieve a repository release by its exact tag name
Get repository gitea_get_repositoryRetrieve metadata and capabilities for one repository
Get repository contents gitea_get_repository_contentsRetrieve file content or directory entries from a repository path
Get signing key gitea_get_signing_keyRetrieve the default GPG signing key used by Gitea to sign commits
Get version gitea_get_versionRetrieve the version of the Gitea application
Get workflow job gitea_get_workflow_jobGet structured status and step details for one Gitea Actions job
Get workflow job logs gitea_get_workflow_job_logsRetrieve the plain-text diagnostic log for a repository Actions job
List branches gitea_list_branchesList branches and their head commits for a Gitea repository
List commits gitea_list_commitsList and filter commits in a repository
List gitignore templates gitea_list_gitignore_templatesRetrieve all available gitignore templates
List issue comments gitea_list_issue_commentsList comments on a repository issue, optionally bounded by update time
List label templates gitea_list_label_templatesRetrieve all available label templates
List license templates gitea_list_license_templatesRetrieve all available license templates
List pull request files gitea_list_pull_request_filesList files changed by a pull request
List pull requests gitea_list_pull_requestsFilter and list pull requests in a repository

Try it: find the Gitea tool you need

Browse the 30 Gitea tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Use Gitea to activitypub person and walk me through the result in plain English.

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Gitea working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Gitea API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Gitea account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Gitea.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Gitea actions to the runtime in a format your agent can reliably use.47 tools for Gitea are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Gitea to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Gitea in the browser, and the 47 tools above work from chat. There is no SDK and no config file, and the Gitea key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

OpenClaw installed the Gitea skill but can't call the tools

The ClawHub skill teaches OpenClaw about Gitea, but the calls run through the ClawLink plugin and your connected account. Make sure Gitea is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

Connection succeeds but no tools appear

Reconnect Gitea from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

"Tool schema not loaded yet" error when calling Gitea tools

Gitea tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Gitea call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Gitea returns 403 or "permission denied" on one action while others work

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

API key setup works but results look incomplete

Double-check that the API key for Gitea has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a OpenClaw Gitea integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Gitea: link your Gitea account once in the browser and OpenClaw can call the Gitea API through 47 ready-made tools — no custom code or token handling.

How do I add Gitea to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Gitea skill from ClawHub, then you click Connect in the dashboard to authorize Gitea. OpenClaw calls the tools from the next message — no config files, and the Gitea key you paste is stored server-side instead of in your environment.

How long does it take to connect Gitea to OpenClaw?

About two minutes. Sign in, click Connect next to Gitea in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Gitea up myself?

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Gitea working from chat.

OpenClaw installed the Gitea skill but can't call the tools

The ClawHub skill teaches OpenClaw about Gitea, but the calls run through the ClawLink plugin and your connected account. Make sure Gitea is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

On this page