Forgejo MCP Server

If you already use Forgejo MCP, the forgejo mcp mcp server is the piece that lets your assistant work with it directly. Connect your AI assistant to Forgejo repositories. Manage issues, pull requests, files, and more through natural language.

What the server does

• "List all my repositories"
• "Create an issue titled 'Bug in login page'"
• "Show me open pull requests in my-org/my-repo"
• "Get the contents of README.md from the main branch"
• "Show me the latest Actions workflow runs in goern/forgejo-mcp"

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• User — The User tool exposed by this server
• get_my_user_info — Get information about the authenticated user
• check_notifications — Check and list user notifications
• get_notification_thread — Get detailed info on a single notification thread
• mark_notification_read — Mark a single notification thread as read
• mark_all_notifications_read — Acknowledge all notifications
• list_repo_notifications — Filter notifications scoped to a single repository
• mark_repo_notifications_read — Mark all notifications in a specific repo as read
• search_users — Search for users
• Repositories — The Repositories tool exposed by this server
• list_my_repos — List all repositories you own
• create_repo — Create a new repository

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

Configuration is passed through the environment: FORGEJO_ACCESS_TOKEN, FORGEJO_USER_AGENT, FORGEJO_URL, COSIGN_PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Forgejo MCP's toolset — User, get_my_user_info, check_notifications and 11 more — is a fair guide to whether it matches your workflow. It is maintained by goern; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Forgejo MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.