Fj FAQs

Question 1

What is Fj-mcp and its primary purpose?

Accepted Answer

Fj-mcp is an MCP (Multi-CLI Proxy) server that exposes the `fj` command-line interface for Forgejo. Its primary purpose is to enable programmatic and automated collaborative software development by allowing agents to interact with Forgejo features via standard I/O.

Question 2

What specific Forgejo features can Fj-mcp manage programmatically?

Accepted Answer

Fj-mcp provides comprehensive programmatic control over Forgejo pull requests (create, view, close, merge, approve), discovery and viewing of repositories and issues, and the ability to create new issues or comment on existing ones.

Question 3

Does Fj-mcp require a local `fj` CLI installation?

Accepted Answer

Yes, Fj-mcp is designed to reuse and expose the capabilities of your local `fj` command-line binary. It acts as an intermediary, wrapping the `fj` CLI's functionality into a standardized MCP server interface for seamless automation workflows.

Question 4

How does Fj-mcp handle pull request approvals if `fj` CLI doesn't support it?

Accepted Answer

For approving pull requests, Fj-mcp directly utilizes the Forgejo HTTP API instead of the `fj` CLI. It requires an appropriate Forgejo token, which can be configured via environment variables like `FORGEJO_TOKEN`.

Question 5

How does Fj-mcp assist automated agents in understanding command execution?

Accepted Answer

Fj-mcp delivers detailed JSON responses for every executed command, which include the command itself, its stdout, stderr, and the exit code. This rich, structured data empowers agents to precisely analyze and reason about command outcomes without fragile parsing.

Fj

Fj

Key Features

Use Cases

Key Features

Use Cases