Respan Gateway CLI
A CLI runs a model and MCP-tool gateway with owned API keys, format translation, routing and request logs.
- 553 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The gateway handles API keys, requests and logs; an explicitly enabled loop invokes configured tools.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/respan-gateway-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The gateway handles API keys, requests and logs; an explicitly enabled loop invokes configured tools.
This is third-party code. Review the repository files before installing.
What it does
Respan Gateway starts a local service between an application and model providers. Clients retain familiar API formats while the gateway translates requests, selects routes and handles retries or fallback. A web interface shows calls, cost and latency. Configured MCP servers and supported tool vendors can be combined at `/mcp`. An optional tool loop lets a model invoke allowed actions within a normal request. Configuration sets client keys, available tools and the step limit.
Who it is for. For developers running their own gateway between an AI application, provider APIs and selected MCP tools.
Good fit when
- Change providers without rewriting a client format.
- Configure a fallback model.
- Combine MCP connections behind one endpoint.
- Inspect calls and restrict clients with keys.
Not a fit when
- You expect model access without owned authorization.
- The service cannot be trusted with provider keys and requests.
- Tools would be enabled without reviewing their permissions.
Example request
Run a test Respan Gateway with my API access and no tool loop, then show one harmless request route.Limitations
The gateway uses your provider credentials and quotas, so retries and hedged requests can increase cost. Without client keys it accepts connections only from this machine and refuses public binding. The tool loop is off by default; when enabling it, set `allow`, `deny` and `max_steps` for a specific task. Requests enter logs and selected tools; inspect the tool list and trace destinations before submitting private data.
How to disable. Stop the gateway and restore client API addresses. Disabling one tool does not stop the gateway; clean credentials and logs separately.
FAQ
How do I create configuration?
Run `respan-gateway init`.
How do I validate it?
Use `respan-gateway check`.
Where is the web interface?
The quick start uses `http://localhost:8080/ui/`.
Does it expose MCP itself?
Yes. `/mcp` merges configured tools, while `/mcp/{name}` serves one server.
How do I disable the loop for one request?
Use the `x-respan-tool-loop: off` header.
Discussion
No questions or reviews yet.
Related
CLI toolsThe CLI runs a model gateway that routes requests across backends and executes MCP tools under configured policies.
A self-hosted gateway routes internal MCP tools, authenticates users and records requests for later review.
AIHelms is an organizational MCP gateway that attributes calls to employee keys and tracks configured per-tool costs.
A self-hosted gateway that merges several MCP servers into one endpoint with auth and tool selection
MCP Gateway
mcp-gateway
A reverse proxy and lifecycle management for MCP servers on Kubernetes and Azure from Microsoft: routing, authorization, roles. For platform teams
A Node.js manager for MCP servers: it starts local servers, connects remote ones and gives a client one address, with a REST API for control
README in short
The service can consume upstream MCP and expose it through its own MCP facade. Supported HTTP tool vendors can also be exposed as MCP.