Ryan Parmeter
e6e1ef2144
BREAKING CHANGE: All binary paths must now be explicitly configured. Changes to code: - Added docker_binary_path setting to GiteaContextServerSettings - Updated find_docker_binary() to require explicit docker path - Clear error messages with platform-specific examples - Consistent approach: no auto-detection for any binaries Changes to documentation: - Updated README.md with docker_binary_path requirement - Rewrote default_settings.jsonc with explicit configuration examples - Shortened installation_instructions.md to fit Zed UI - Added 'which' command instructions to find binary paths - Documented common paths for macOS, Linux, Windows - Explained WASM limitations clearly Why this approach: - WASM cannot access PATH reliably (especially on macOS) - WASM cannot detect host OS - WASM cannot check file existence - Explicit configuration is reliable and works everywhere - Users have full control over which binaries are used - Configuration is done once and works consistently This completes the simplification: ✅ No auto-detection attempts ✅ Clear, actionable error messages ✅ Comprehensive documentation ✅ Works reliably on Linux, macOS, and Windows ✅ Tested on Linux x86_64 and macOS M4
863 B
863 B
Tendril: Gitea MCP for Zed
1. Install Gitea MCP Binary
macOS (Homebrew):
brew install gitea/tap/gitea-mcp-server
# Installs to: /opt/homebrew/bin/gitea-mcp-server
Linux:
# Download from: https://gitea.com/gitea/gitea-mcp/releases
wget https://gitea.com/gitea/gitea-mcp/releases/download/v1.0.0/gitea-mcp-linux-amd64
chmod +x gitea-mcp-linux-amd64
sudo mv gitea-mcp-linux-amd64 /usr/local/bin/gitea-mcp
Or use Docker (requires Docker installed)
2. Get Gitea Access Token
- Log in to your Gitea instance
- Settings → Applications → Generate New Token
- Copy the token
3. Configure Zed (Cmd/Ctrl + ,)
Find your binary path: which gitea-mcp-server or which docker
Add gitea_mcp_binary_path (or use_docker: true + docker_binary_path)
More help: See full README.md in extension directory