ngsrv-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NGSRV_API_TOKEN | No | Your ngsrv API token (optional for quick start, required for account features) |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tunnel.startA | Expose a local HTTP server on a public HTTPS URL via ngsrv. Returns public_url and local_port. Use for webhooks, OAuth callbacks, and sharing dev servers. Call tunnel.list afterward to see active tunnels. |
| tunnel.listA | List HTTPS tunnels started by this MCP process in the current session. Returns port, public_url, and started_at for each tunnel. Call this before tunnel.stop to confirm which port to close. |
| tunnel.stopA | Stop an ngsrv tunnel started by this MCP session. Pass the same port given to tunnel.start. Call tunnel.list first if you are unsure which ports are active. |
| token.provisionA | Obtain a 12-hour ngsrv agent token for tunnel commands. Uses NGSRV_API_TOKEN when set; otherwise starts a free device trial (no signup). Returns token_prefix and expiry — not the full secret. |
| docs.installA | Return ngsrv CLI install commands and MCP client configuration snippets. Call when the user asks how to install ngsrv, configure Cursor, or use npx. Does not start a tunnel. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tunnel.quickstart | Step-by-step prompt to expose a local dev server (default port 3000) on a public HTTPS URL. |
| docs.setup | Shows how to add ngsrv to Cursor or Claude Desktop using npx and optional API token. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| quickstart | Install commands and links for ngsrv CLI, npx @ngsrv/cli, and ngsrv-mcp. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: installation documentation, token provisioning, and tunnel lifecycle management (list, start, stop). There is no overlap or ambiguity between them.
All tool names follow a consistent <category>.<action> pattern with lowercase and dots (e.g., docs.install, tunnel.start). No mixing of conventions or styles.
Five tools cover the essential operations for the ngsrv tunnel service: installation, token provisioning, and managing tunnels. The count is well-scoped and not excessive.
The tool surface covers the core workflow (install, auth, start/list/stop tunnels). Minor gaps exist, such as no tool to inspect token details or restart tunnels, but the set is functional for typical use cases.