fix: correct gitea-mcp naming and remove GitCoffee references

This commit is contained in:
2026-04-10 22:18:58 -07:00
parent a8a71e7c87
commit 6d7cadae1b
2 changed files with 12 additions and 12 deletions
+11 -11
View File
@@ -1,18 +1,18 @@
# GitCoffee MCP Setup for OpenClaw # Gitea MCP Setup for OpenClaw
This guide explains how to set up GitCoffee MCP with per-agent Gitea account isolation in OpenClaw. This guide explains how to set up Gitea MCP with per-agent Gitea account isolation in OpenClaw.
## Structure ## Structure
``` ```
gitea-mcp-mcp/ gitea-mcp/
├── mcp/ # MCP server source code (Go) ├── mcp/ # MCP server source code (Go)
└── AGENTS.md # This file - OpenClaw setup guide └── AGENTS.md # This file - OpenClaw setup guide
``` ```
## Architecture Overview ## Architecture Overview
The GitCoffee MCP server provides Gitea tools via the Model Context Protocol (MCP). Each MCP instance uses a single Gitea token, making it ideal for per-agent isolation. The Gitea MCP server provides Gitea tools via the Model Context Protocol (MCP). Each MCP instance uses a single Gitea token, making it ideal for per-agent isolation.
**Key Features:** **Key Features:**
- stdio mode (default): For local MCP clients - stdio mode (default): For local MCP clients
@@ -39,7 +39,7 @@ The GitCoffee MCP server provides Gitea tools via the Model Context Protocol (MC
```bash ```bash
cd mcp cd mcp
make build make build
cp gitea-mcp ~/.bun/bin/gitea-mcp-mcp cp gitea-mcp ~/.bun/bin/gitea-mcp
``` ```
### Step 2: Run Multiple MCP Instances ### Step 2: Run Multiple MCP Instances
@@ -48,10 +48,10 @@ Each agent needs its own MCP server instance with its own token:
```bash ```bash
# Friday's MCP (runs on port 8081) # Friday's MCP (runs on port 8081)
gitea-mcp-mcp --host https://gitea.example.com --port 8081 --token <YOUR_GITEA_TOKEN> & gitea-mcp --host https://gitea.example.com --port 8081 --token <YOUR_GITEA_TOKEN> &
# Karti's MCP (runs on port 8082) # Karti's MCP (runs on port 8082)
gitea-mcp-mcp --host https://gitea.example.com --port 8082 --token <YOUR_GITEA_TOKEN> & gitea-mcp --host https://gitea.example.com --port 8082 --token <YOUR_GITEA_TOKEN> &
``` ```
### Step 3: Configure MCP Servers in OpenClaw ### Step 3: Configure MCP Servers in OpenClaw
@@ -66,14 +66,14 @@ Add to `~/.openclaw/openclaw.json`:
"config": { "config": {
"mcpServers": { "mcpServers": {
"gitea-mcp-friday": { "gitea-mcp-friday": {
"command": "gitea-mcp-mcp", "command": "gitea-mcp",
"args": ["--host", "https://gitea.example.com", "--port", "8081"], "args": ["--host", "https://gitea.example.com", "--port", "8081"],
"env": { "env": {
"GITEA_ACCESS_TOKEN": "<YOUR_GITEA_TOKEN>" "GITEA_ACCESS_TOKEN": "<YOUR_GITEA_TOKEN>"
} }
}, },
"gitea-mcp-karti": { "gitea-mcp-karti": {
"command": "gitea-mcp-mcp", "command": "gitea-mcp",
"args": ["--host", "https://gitea.example.com", "--port", "8082"], "args": ["--host", "https://gitea.example.com", "--port", "8082"],
"env": { "env": {
"GITEA_ACCESS_TOKEN": "<YOUR_GITEA_TOKEN>" "GITEA_ACCESS_TOKEN": "<YOUR_GITEA_TOKEN>"
@@ -192,13 +192,13 @@ To add a new agent (e.g., "edith"):
1. Run a new MCP instance: 1. Run a new MCP instance:
```bash ```bash
gitea-mcp-mcp --host https://gitea.example.com --port 8083 --token <YOUR_GITEA_TOKEN> & gitea-mcp --host https://gitea.example.com --port 8083 --token <YOUR_GITEA_TOKEN> &
``` ```
2. Add to mcpServers in openclaw.json: 2. Add to mcpServers in openclaw.json:
```json ```json
"gitea-mcp-edith": { "gitea-mcp-edith": {
"command": "gitea-mcp-mcp", "command": "gitea-mcp",
"args": ["--host", "https://gitea.example.com", "--port", "8083"], "args": ["--host", "https://gitea.example.com", "--port", "8083"],
"env": { "GITEA_ACCESS_TOKEN": "<YOUR_GITEA_TOKEN>" } "env": { "GITEA_ACCESS_TOKEN": "<YOUR_GITEA_TOKEN>" }
} }
+1 -1
View File
@@ -2,7 +2,7 @@
set -e set -e
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
BINARY_DIR="${HOME}/.cache/gitea-mcp-mcp" BINARY_DIR="${HOME}/.cache/gitea-mcp"
BINARY="$BINARY_DIR/gitea-mcp" BINARY="$BINARY_DIR/gitea-mcp"
mkdir -p "$BINARY_DIR" mkdir -p "$BINARY_DIR"