mcp-proxy-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY_BRIDGE_CONFIG | No | Config file path. | |
| PROXY_BRIDGE_TARGETS | No | Comma-separated targets. | |
| PROXY_BRIDGE_GIT_SCOPE | No | Comma-separated git URL prefixes. | |
| PROXY_BRIDGE_CHECK_PORT | No | Target port (number as string). | |
| PROXY_BRIDGE_HOOK_EXTRA | No | Comma-separated extra trigger regexes. | |
| PROXY_BRIDGE_LAUNCH_CMD | No | Launch command. | |
| PROXY_BRIDGE_PROXY_HOST | No | Proxy host. | |
| PROXY_BRIDGE_PROXY_PORT | No | Proxy port. | |
| PROXY_BRIDGE_LAUNCH_ARGS | No | Launch args (JSON array or space-split). | |
| PROXY_BRIDGE_PROXY_SCHEME | No | Proxy scheme (http or socks5). | |
| PROXY_BRIDGE_PROCESS_NAMES | No | Comma-separated process names. | |
| PROXY_BRIDGE_SET_GIT_PROXY | No | 0 disables git proxy. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ensure_accessA | Ensure the target host (default: first configured target) is reachable. Checks direct first; if it fails, launches the proxy, waits for the port, and verifies through the proxy. Returns status + proxy URL. |
| checkB | Test HTTPS reachability of a target host. useProxy=true routes through the configured proxy; false=direct. |
| statusB | Report whether the proxy process is running (best-effort), the proxy port is open, and the configured targets. |
| start_proxyA | Launch the configured proxy client (detached). Returns whether it was launched vs. already running. |
| stop_proxyA | Best-effort kill of the configured proxy process(es). |
| proxy_infoA | Return the proxy URL plus copy-paste hints for HTTPS_PROXY env vars and URL-scoped git config (and how to unset). |
| set_git_proxyA | Apply the URL-scoped git http proxy for the configured targets (idempotent). Useful after the proxy is up. |
| show_configA | Return the resolved configuration and the config file path (for debugging). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Proxy Info | Proxy URL and usage hints |
| Resolved Config | Resolved configuration |
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.