docs: add per-client MCP setup instructions
Expandable sections for Antigravity, Claude Code, generic MCP clients, and Codex/non-MCP fallback to CLI scripts.
This commit is contained in:
@@ -37,15 +37,80 @@ Any MCP-compatible agent (Antigravity, Claude Code, etc.) can call these tools n
|
||||
|
||||
### Setup
|
||||
|
||||
#### 1. Install dependencies
|
||||
|
||||
```bash
|
||||
# Install dependencies
|
||||
cd /Users/jasonwalker/Development/Gitea-Tools
|
||||
python3 -m venv venv # skip if venv already exists
|
||||
source venv/bin/activate
|
||||
pip install "mcp[cli]"
|
||||
```
|
||||
|
||||
The server is configured in `mcp_config.json` and runs automatically when Antigravity starts.
|
||||
Restart Antigravity to load the server after first setup.
|
||||
#### 2. Configure your AI client
|
||||
|
||||
The MCP server uses **stdio transport** — each client starts it as a subprocess.
|
||||
Add the config below to your client, then restart it.
|
||||
|
||||
<details>
|
||||
<summary><strong>Antigravity (Google)</strong></summary>
|
||||
|
||||
Add to `~/.gemini/antigravity-ide/mcp_config.json` inside `"mcpServers"`:
|
||||
|
||||
```json
|
||||
"gitea-tools": {
|
||||
"command": "/Users/jasonwalker/Development/Gitea-Tools/venv/bin/python3",
|
||||
"args": ["/Users/jasonwalker/Development/Gitea-Tools/mcp_server.py"],
|
||||
"env": {}
|
||||
}
|
||||
```
|
||||
|
||||
Restart Antigravity to load the server. Tools appear as lazy-loaded MCP tools
|
||||
(call via `call_mcp_tool` with `ServerName: "gitea-tools"`).
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary><strong>Claude Code (Anthropic)</strong></summary>
|
||||
|
||||
Add to `~/.claude.json` (global) or `.mcp.json` in the project root:
|
||||
|
||||
```json
|
||||
{
|
||||
"mcpServers": {
|
||||
"gitea-tools": {
|
||||
"command": "/Users/jasonwalker/Development/Gitea-Tools/venv/bin/python3",
|
||||
"args": ["/Users/jasonwalker/Development/Gitea-Tools/mcp_server.py"]
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Restart Claude Code. Tools appear as `mcp__gitea-tools__gitea_create_issue`, etc.
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary><strong>Any MCP-compatible client</strong></summary>
|
||||
|
||||
The server is a standard MCP stdio server. Point your client at:
|
||||
|
||||
- **Command:** `/Users/jasonwalker/Development/Gitea-Tools/venv/bin/python3`
|
||||
- **Args:** `["/Users/jasonwalker/Development/Gitea-Tools/mcp_server.py"]`
|
||||
- **Transport:** `stdio`
|
||||
|
||||
No environment variables needed — auth is handled via macOS keychain.
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary><strong>Codex / non-MCP tools</strong></summary>
|
||||
|
||||
OpenAI Codex and other tools that don't support MCP can use the CLI scripts
|
||||
directly. See the [CLI Scripts](#cli-scripts) section below.
|
||||
|
||||
```bash
|
||||
# Example: Codex can shell out to the scripts
|
||||
python3 /Users/jasonwalker/Development/Gitea-Tools/create_issue.py \
|
||||
--remote prgs --title "Bug report" --body "Details here"
|
||||
```
|
||||
</details>
|
||||
|
||||
## CLI Scripts
|
||||
|
||||
|
||||
Reference in New Issue
Block a user