Authenticated HTTP MCP server for Forgejo/Gitea APIs.
  • JavaScript 100%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-08-16 15:53:29 +00:00
deploy Initial forgejo MCP server 2026-08-16 15:49:06 +00:00
src Improve MCP tool descriptions 2026-08-16 15:53:29 +00:00
test Initial forgejo MCP server 2026-08-16 15:49:06 +00:00
.env.example Initial forgejo MCP server 2026-08-16 15:49:06 +00:00
.gitignore Initial forgejo MCP server 2026-08-16 15:49:06 +00:00
package-lock.json Initial forgejo MCP server 2026-08-16 15:49:06 +00:00
package.json Initial forgejo MCP server 2026-08-16 15:49:06 +00:00
README.md Initial forgejo MCP server 2026-08-16 15:49:06 +00:00

forgejo-mcp

Authenticated Streamable HTTP MCP server for https://git.kokpit.sk.

Runtime

  • Local server: http://127.0.0.1:4120
  • Public endpoint after Caddy deploy: https://forgejo-mcp.pk01.sk/mcp
  • Health check: https://forgejo-mcp.pk01.sk/health

MCP clients must send:

Authorization: Bearer <token>

If MCP_AUTH_TOKEN is not set, the service creates a random token in:

/home/pk01/apps/forgejo-mcp/data/mcp-auth-token

Forgejo API auth is loaded from FORGEJO_TOKEN, FORGEJO_TOKEN_FILE, or the default tea login in /home/pk01/.config/tea/config.yml.

Mutating Forgejo tools are disabled unless FORGEJO_ALLOW_WRITE=true.