mcp-proxy-bridge
Related Servers
Alternatives to mcp-proxy-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Codex chat to use the Claude Code harness for repository consultation and editing, routing through GPT models via a local proxy.1 npmMIT
- FlicenseNot gradedqualityCmaintenanceA zero-config local desktop proxy gateway for AI coding agents, providing model failovers, spend caps, and 1-click MCP tool syncing across multiple client environments.-
- -licenseNot gradedqualityNot gradedmaintenanceA proxy server that enables communication between clients (like Claude AI or VS Code) and JetBrains IDEs, allowing AI assistants to access IDE functionality.0-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely access authenticated services (HTTP, SSH, SMTP) without exposing secrets, by acting as a server-side proxy that injects authentication.MIT
- AlicenseNot gradedqualityCmaintenanceDiagnoses proxy misconfigurations that break AI coding tools like Cursor, VS Code, and Windsurf.1MIT
- AlicenseAqualityCmaintenanceConnects AI tools to local dev servers, enabling them to view pages, call APIs, read/edit files, and run commands with safety guardrails.13MIT
TDQS
Scored across 8 tools
Most tools have distinct purposes, but 'check' and 'ensure_access' both test reachability; 'ensure_access' is a higher-level operation that may also launch the proxy, causing slight ambiguity.
Tool names use a mix of conventions: some are verbs only ('check'), some are verb_noun ('start_proxy'), and some are noun_only ('status') or noun_info ('proxy_info'), lacking a consistent pattern.
With 8 tools, the set is well-scoped for managing a proxy bridge, covering essential operations without unnecessary bloat.
The tool set covers core proxy lifecycle (start/stop/status), reachability testing, configuration access, and git proxy setup. Missing direct tool for managing proxy targets, but config editing may be external.