[MCP] - Story 1: Tooling Spike & Fedora Forge Compatibility #487

New issue

Open

opened 2026-04-02 08:38:24 +00:00 by humaton · 0 comments

humaton commented

2026-04-02 08:38:24 +00:00

Owner

Summary

Before committing to an architecture, we need to validate that the upstream goern/forgejo-mcp project works seamlessly with our specific Fedora Forge instance. This spike involves compiling the project locally and running basic MCP tool calls against a staging environment to identify any API discrepancies or missing features.

Details

Tasks

Set up a local Go development environment (Go 1.24+ required).
Clone the goern/forgejo-mcp repository and compile the binary.
Provision a test Personal Access Token (PAT) on the Fedora Forge staging instance.
Run the MCP server locally using the STDIO transport method.
Connect a local client (e.g., the official MCP Inspector or Claude Desktop) to the running binary.
Test core capabilities: repository listing, file reading, and issue querying.

Acceptance Criteria

The binary compiles successfully without critical warnings.
The server connects to the Fedora Forge staging instance using the FORGEJO_ACCESS_TOKEN environment variable.
An AI client can successfully read a spec file from a test repository via the MCP server.
A brief summary of findings (performance, bugs, or limitations) is published to the Epic thread.

### Summary Before committing to an architecture, we need to validate that the upstream `goern/forgejo-mcp` project works seamlessly with our specific Fedora Forge instance. This spike involves compiling the project locally and running basic MCP tool calls against a staging environment to identify any API discrepancies or missing features. ### Details **Tasks** 1. Set up a local Go development environment (Go 1.24+ required). 2. Clone the `goern/forgejo-mcp` repository and compile the binary. 3. Provision a test Personal Access Token (PAT) on the Fedora Forge staging instance. 4. Run the MCP server locally using the STDIO transport method. 5. Connect a local client (e.g., the official MCP Inspector or Claude Desktop) to the running binary. 6. Test core capabilities: repository listing, file reading, and issue querying. **Acceptance Criteria** * The binary compiles successfully without critical warnings. * The server connects to the Fedora Forge staging instance using the `FORGEJO_ACCESS_TOKEN` environment variable. * An AI client can successfully read a spec file from a test repository via the MCP server. * A brief summary of findings (performance, bugs, or limitations) is published to the Epic thread.