Forgejo MCP Server
Provides tools to interact with Forgejo repositories, including listing repositories, getting repository information, managing issues (list and create), and reading file contents.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Forgejo MCP Server list my repositories"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Forgejo MCP Server
A Model Context Protocol (MCP) server that provides Claude Desktop with tools to interact with Forgejo repositories.

Features
List repositories
Get repository information
List issues with filtering by state
Create new issues
Read file contents from repositories
List, view, and create pull requests
Related MCP server: forgejo-mcp
Installation
git clone https://github.com/nsvk13/forgejo-mcp-server
cd forgejo-mcp-server
npm install
npm run buildConfiguration
Environment Variables
Set the following environment variables:
FORGEJO_BASE_URL: Your Forgejo instance URL (e.g.,https://your-forgejo.com)FORGEJO_TOKEN: Your Forgejo API token
Generating a Forgejo API Token
Go to your Forgejo instance
Navigate to Settings → Applications
Generate a new token with appropriate permissions
Copy the token for use in configuration
Claude Desktop Configuration
Add the following to your Claude Desktop configuration file:
Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"forgejo": {
"command": "node",
"args": ["/absolute/path/to/forgejo-mcp-server/dist/index.js"],
"env": {
"FORGEJO_BASE_URL": "https://your-forgejo-instance.com",
"FORGEJO_TOKEN": "your_api_token_here"
}
}
}
}Replace the path and credentials with your actual values.
Usage
After configuration, restart Claude Desktop. You can then use commands like:
"List my Forgejo repositories"
"Show issues in repository owner/repo-name"
"Create an issue in repository with title 'Bug report'"
"Show the contents of README.md from repository"
Available Tools
list_repositories: Get list of user repositoriesget_repository: Get detailed repository informationlist_issues: List issues with optional state filteringcreate_issue: Create a new issueget_file_content: Read file contents from repositorylist_pull_requests: List pull requests with optional state filteringget_pull_request: Get a single pull request by its numbercreate_pull_request: Open a new pull request from a head branch into a base branch
Development
# Build the project
npm run build
# Run in development mode
npm run devRequirements
Node.js 18 or higher
TypeScript
Valid Forgejo instance with API access
Available Tools
8 toolscreate_issueC
Create a new issue
Inputs: repo (required), owner (required), title (required), body.
create_pull_requestB
Open a new pull request from a head branch into a base branch
Inputs: base (required), head (required), repo (required), owner (required), +2 more.
get_file_contentC
Get file content from repository
Inputs: path (required), repo (required), owner (required), ref.
get_pull_requestB
Get a single pull request by its number
Inputs: repo (required), index (required), owner (required).
get_repositoryC
Get repository information
Inputs: repo (required), owner (required).
list_issuesC
Get list of repository issues
Inputs: repo (required), owner (required), state.
list_pull_requestsC
Get list of repository pull requests
Inputs: repo (required), owner (required), state.
list_repositoriesB
Get list of user repositories
Inputs: username.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct resource (issue, PR, file, repository) with specific actions, so there is no ambiguity. An agent can clearly differentiate between creating issues, listing pull requests, or getting file content.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_issue, get_file_content), making them predictable and easy to understand.
With 8 tools covering core operations for issues, pull requests, repositories, and file content, the scope is well-balanced for a Git forge server—neither too sparse nor overwhelming.
The tool set covers create and read operations for issues and PRs, plus repository and file access, but notably lacks update/delete operations (e.g., update_issue, merge_pull_request) and repository creation, leaving notable gaps for full lifecycle management.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP Server for JFrog, providing tools for development and artifact management.
GitHub Copilot MCP: code, repo, PR, workflow tools for AI assistants.
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.55 npm-
- AlicenseBqualityCmaintenanceA Model Context Protocol (MCP) server for Forgejo and Gitea instances, enabling AI assistants to interact with repositories, issues, pull requests, and more.100636 npm17MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Forgejo that exposes tools for pull requests, repositories, and issues, leveraging the local fj CLI.-
- AlicenseNot gradedqualityCmaintenanceA local MCP server that connects Claude directly to your Gitea instance, enabling management of repositories, issues, pull requests, files, and commit history.MIT