Start free

Connect Codex to Gitea

Codex reaches Gitea through one Flowplane address. You add Gitea once in Flowplane, add that address to Codex, and sign in. Read code, issues, pull requests and Actions logs in your own Gitea, and open, review or merge with your approval.

Connect Gitea →Set up your assistant
Tools
24 read · 19 change
Sign-in
Own account or shared key
Approval, by default
Changes wait for you
MCP server
Flowplane’s tools
  1. 1

    Add Gitea in Flowplane

    In the Flowplane console, add Gitea, type the address you open Gitea at, and either enter the OAuth application’s client ID and secret or paste an access token.

    Two ways. Sign in with Gitea: a Gitea administrator registers an OAuth2 application in your Gitea once, and then each person signs in and acts as themselves. Or an access token: one person makes a token in Gitea (Settings, Applications) and pastes it, and the assistant acts with that account’s rights, cut down to the scopes ticked. Flowplane keeps it sealed; the assistant never sees it.

    Connect Gitea →

  2. 2

    Add Flowplane to Codex

    Your address is shown in the Flowplane console; it looks like

    https://mcp.flowplane.eu/<your-label>

    1. Add the server with the first command below.
    2. Sign in with the second: your browser opens Flowplane; sign in and allow Codex.
    3. In the IDE extension: MCP servers › Add server, choose Streamable HTTP, paste https://mcp.flowplane.eu/<your-label>, then Authenticate.
    codex mcp add flowplane --url https://mcp.flowplane.eu/<your-label>
codex mcp login flowplane

    Steps checked against the vendor’s documentation (OpenAI)

  3. 3

    Ask Codex

    • “Which pull requests in acme/website are still open, and which have failing checks?”
    • “Show me the diff of PR 42 and sum up what it changes.”
    • “Why did the last Actions run on main fail? Read the log of the failing job.”
    • “Open an issue in acme/api: the export button times out on large files, label it bug.”
    • “Merge pull request 57 in acme/website once its checks pass.”
What it can do

What Codex can do in Gitea

Gitea is the self-hosted Git forge many teams run on their own servers. Through Flowplane an AI assistant can read repositories, files, commits, pull requests with their diffs and reviews, issues, releases and the logs of Actions jobs. It can open issues and pull requests, comment, review, commit a file or merge, and each of those changes waits for your approval by default.

Reads24

  • List repositoriesYours, an owner's, or found by namelist_repos
  • Get repoA repository's settings and countsget_repo
  • List branchesThe branches of a repositorylist_branches
  • Read a fileA file's text, cut to a sizeget_file
  • List a directoryFiles and folders, one level or all belowlist_dir
  • List commitsThe commits of a branch or pathlist_commits
  • Get commitOne commit with the files it changedget_commit
  • Compare two refsThe commits one branch has over anothercompare
  • Get statusThe checks on a commit: passing or notget_status
  • List prsThe pull requests of a repositorylist_prs
  • Get prOne pull requestget_pr
  • List pr filesThe files a pull request changeslist_pr_files
  • Read a pull request's diffThe changes as a unified diff, cut to a sizeget_pr_diff
  • List a pull request's reviewsReviews, or the comments of one reviewlist_pr_reviews
  • List issuesThe issues of a repository, filteredlist_issues
  • Get issueOne issueget_issue
  • List commentsThe discussion on an issue or pull requestlist_comments
  • Search issuesIssues and pull requests across repositoriessearch_issues
  • List labelsA repository's labels, or an organisation'slist_labels
  • List milestonesThe milestones of a repositorylist_milestones
  • List releasesReleases, or one by its tag with its noteslist_releases
  • List Actions runsWorkflow runs, or the jobs of one runlist_action_runs
  • Read a job's logThe end of an Actions job's logget_action_job_log
  • List notificationsYour unread notificationslist_notifications

Changesasks first19

  • Create issueOpen a new issue, asked firstcreate_issue
  • Edit issueChange an issue or close it, asked firstedit_issue
  • Add commentComment on an issue or pull request, asked firstadd_comment
  • Edit commentChange a comment's text, asked firstedit_comment
  • Change labelsAdd or remove an issue's labels, asked firstupdate_labels
  • Create labelMake a new label, asked firstcreate_label
  • Create prOpen a pull request, asked firstcreate_pr
  • Edit prChange a pull request, asked firstedit_pr
  • Request reviewAsk people for a review, asked firstrequest_review
  • Submit reviewApprove, request changes or comment, asked firstsubmit_review
  • Create branchMake a new branch, asked firstcreate_branch
  • Write a fileCommit a file's new text, asked firstcreate_or_update_file
  • Create releasePublish a release, asked firstcreate_release
  • Merge a pull requestMerge it into its branch, asked first by defaultmerge_pr
  • Delete a branchRemove a branch, asked first by defaultdelete_branch
  • Delete a fileRemove a file in a commit, asked first by defaultdelete_file
  • Delete a releaseRemove a release, asked first by defaultdelete_release
  • Delete a labelRemove a label, asked first by defaultdelete_label
  • Delete a commentRemove a comment, asked first by defaultdelete_comment
FAQ

Questions

Which way of signing in should we use?
Sign in with Gitea when several people use it: each acts as themselves. It needs Gitea 1.23 or later for the scopes to hold, and a Gitea reachable from the internet on port 443 with a public certificate. Use an access token for one person, for an older Gitea, or for a Gitea behind a firewall (through a tunnel) or with a certificate from your own authority.
What can the assistant change in Gitea?
Issues, comments, labels, pull requests, reviews, branches, files and releases, and every change waits for your approval by default. Merging a pull request and every delete cannot be undone, so they wait for your approval by default. Creating, deleting or transferring repositories, collaborators and teams, webhooks, deploy keys, branch protection, secrets, packages, administration, force merges and rerunning or cancelling Actions are left out on purpose.
Which Gitea versions does it work with?
Gitea 1.22 and later. Actions runs and job logs need 1.25. Forgejo speaks the same API for most of this, without branch search and a few filters.
Does Codex see the password or key for Gitea?
No. You sign in to Gitea through Flowplane, which keeps that sign-in sealed. Codex only gets a Flowplane sign-in for you, which you can revoke in the console.
Can Codex change things in Gitea without asking?
Not by default: every change in Gitea waits for your approval in the browser. Your workspace’s rules decide, per tool.
Your assistant

Other assistants with Gitea

Everything about Gitea and Flowplane →

Flowplane is not affiliated with or endorsed by Gitea’s maker; the name and logo only identify the app. Pricing

Let your AI work with your data. Safely, from today.

Free for yourself, set up in a minute. For your team or company, we’re happy to help you get started.

Start free →Book a call