MCP server for managing Forgejo Projects/Kanban boards
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"forgejo-projects-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# forgejo-projects-mcp An MCP server that lets an AI agent manage **Forgejo Projects / Kanban boards**, which Forgejo does **not** expose over its REST API. It works by driving the same internal web routes the browser uses, authenticated with a session cookie. HTTP is done through Playwright's `APIRequestContext`, so **no browser binary is downloaded** — only the `playwright` Python package is needed. See the [automation reference](https://github.com/UnwantedForeignCloudProvider/ForgejoProjectsMCP/blob/main/docs/forgejo-projects-automation-reference.md) for the reverse-engineered endpoints this is built on. ## ⚠️ This is a janky backend — do not rely on it for production Forgejo exposes **no API** for Projects/Kanban, so this tool logs in as a real user and drives **undocumented, unversioned internal web routes**, scraping HTML for ids and board state. A Forgejo upgrade can change that markup and break things. The client adapts to the instance version, and every published release from 1.20 to 16 is exercised end to end by an automated integration suite — but that only means known differences are handled, not that the approach is robust. Treat it as a best-effort stop-gap for personal use, test against a throwaway repo, and migrate if Forgejo ships a real Projects API. Details: [Limitations and risk](https://github.com/UnwantedForeignCloudProvider/ForgejoProjectsMCP/blob/main/docs/architecture.md#limitations-and-risk). ## Prerequisites - **[uv](https://docs.astral.sh/uv/)** — used to install and run the tool. Install it from the official guide: <https://docs.astral.sh/uv/getting-started/installation/>. ## Installation All methods install a `forgejo-projects-mcp` executable onto your PATH (in uv's tool bin directory). If uv warns that the directory isn't on your PATH, run `uv tool update-shell` once and restart your shell. Verify with `forgejo-projects-mcp --help` (or `uv tool list`). No `playwright install` step is needed — the tool uses Playwright's …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.