Implement MCP server in Gitea #14969

New Issue

GiteaMirror · 2025-11-02T11:26:57-06:00

GiteaMirror commented

2025-11-02 11:26:57 -06:00

Originally created by @lunny on GitHub (Sep 16, 2025).

Feature Description

Gitea’s official MCP server has been released at https://gitea.com/gitea/gitea-mcp. However, if Gitea itself implements the protocol directly, no additional deployment will be required.

Screenshots

No response

Originally created by @lunny on GitHub (Sep 16, 2025). ### Feature Description Gitea’s official MCP server has been released at https://gitea.com/gitea/gitea-mcp. However, if Gitea itself implements the protocol directly, no additional deployment will be required. ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 11:26:57 -06:00

GiteaMirror commented

2025-11-02 11:26:58 -06:00

@silverwind commented on GitHub (Sep 17, 2025):

I agree it should be part of the main application, but disabled by default.

@silverwind commented on GitHub (Sep 17, 2025): I agree it should be part of the main application, but disabled by default.

GiteaMirror commented

2025-11-02 11:26:59 -06:00

@techknowlogick commented on GitHub (Sep 17, 2025):

I think we should still have it separate as it can evolve as rapidly as it needs to and if there are changes that are urgent then we don't need to affect the project releases

@techknowlogick commented on GitHub (Sep 17, 2025): I think we should still have it separate as it can evolve as rapidly as it needs to and if there are changes that are urgent then we don't need to affect the project releases

GiteaMirror commented

2025-11-02 11:26:59 -06:00

@seuros commented on GitHub (Sep 18, 2025):

I agree with @techknowlogick on keeping it separate.

MCP is a protocol used by LLMs that's still evolving rapidly. Having it as a separate component allows users to:

Upgrade or downgrade independently of Gitea releases
Extend functionality (like I've done)
Keep up with protocol changes without waiting for Gitea release cycles

The flexibility of a separate deployment outweighs the convenience of integration, especially for a rapidly evolving protocol.

@seuros commented on GitHub (Sep 18, 2025): I agree with @techknowlogick on keeping it separate. MCP is a protocol used by LLMs that's still evolving rapidly. Having it as a separate component allows users to: - Upgrade or downgrade independently of Gitea releases - Extend functionality (like I've done) - Keep up with protocol changes without waiting for Gitea release cycles The flexibility of a separate deployment outweighs the convenience of integration, especially for a rapidly evolving protocol.

GiteaMirror commented

2025-11-02 11:26:59 -06:00

@steviee commented on GitHub (Oct 16, 2025):

If there's enough interest I'd commit some time into setting up a docker-compose environment with documentation regarding the quick out-of-the-box experience of having Gitea hosted along its mcp service for SSE access.

Ok, I'll probably look into it anyways. 🤷🏻

@steviee commented on GitHub (Oct 16, 2025): If there's enough interest I'd commit some time into setting up a docker-compose environment with documentation regarding the quick out-of-the-box experience of having Gitea hosted along its mcp service for SSE access. Ok, I'll probably look into it anyways. 🤷🏻

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14969