poly-git-mcp

The server executes external CLI commands (gh, glab, tea) and makes API calls (Bitbucket) using Deno's --allow-run and --allow-net permissions. It constructs command arguments by concatenating user-provided inputs, which, while passed as an array (mitigating shell injection in Deno), means the server delegates powerful actions based on client input. The security boundary relies heavily on the user's local Git forge authentication (e.g., GITHUB_TOKEN, GitLab/Gitea CLI logins, Bitbucket app passwords). Users must ensure tokens have minimal necessary scopes, carefully review tool calls from MCP clients, and understand that the MCP client can perform any action allowed by the provided credentials. No hardcoded secrets were found, and the code does not use `eval` or obfuscation.