store: Local Gitea MCP server setup via @boringstudio_org/gitea-mcp (npm stdio)

This commit is contained in:
Cal Corum 2026-02-25 12:40:34 -06:00
parent cb9f818e47
commit 50dd9ff943

View File

@ -0,0 +1,42 @@
---
id: d56855c9-96d1-4017-ba9e-bb18c83b3661
type: configuration
title: "Local Gitea MCP server setup via @boringstudio_org/gitea-mcp (npm stdio)"
tags: [gitea, mcp, claude-code, configuration, claude-home, npm]
importance: 0.7
confidence: 0.8
created: "2026-02-25T18:40:34.384448+00:00"
updated: "2026-02-25T18:40:34.384448+00:00"
---
# Configuration: Local Gitea MCP Server
## Package
`@boringstudio_org/gitea-mcp` v1.8.0 via `npx` (stdio transport)
Note: The official `docker.gitea.com/gitea-mcp-server` Docker image is NOT available as an npm package. `@boringstudio_org/gitea-mcp` is the best npm alternative for local stdio use.
## Required Environment Variables
- `GITEA_API_URL` — must include `/api/v1` suffix, e.g. `https://git.manticorum.com/api/v1`
- `GITEA_TOKEN` — sourced from tea CLI config at `~/.config/tea/config.yml`
## ~/.claude.json entry
```json
"gitea-mcp": {
"command": "npx",
"args": ["@boringstudio_org/gitea-mcp"],
"env": {
"GITEA_API_URL": "https://git.manticorum.com/api/v1",
"GITEA_TOKEN": "<token from ~/.config/tea/config.yml>"
}
}
```
## Notes
- Replaced the Docker MCP Gateway remote HTTP connection (LXC 303)
- Runs on demand via npx, no persistent process required
- This replaced the `docker-mcp-gateway` MCP server entry for Gitea