nginx-proxy-manager-mcp
by linuskang
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP bind address, default 0.0.0.0 | 0.0.0.0 |
| MCP_PORT | No | HTTP port, default 3000 | 3000 |
| NPM_DEBUG | No | Verbose stderr logging, default false | false |
| NPM_EMAIL | No | Admin email (NPM_TOKEN alternative) | |
| NPM_TOKEN | No | Pre-existing JWT token (takes precedence over email/password) | |
| MCP_ENDPOINT | No | HTTP endpoint path, default /mcp | /mcp |
| NPM_BASE_URL | Yes | Base URL of NPM, e.g. http://npm.local:81 (no trailing slash) | |
| NPM_PASSWORD | No | Admin password (NPM_TOKEN alternative) | |
| MCP_TRANSPORT | No | stdio (default) or http | stdio |
| NPM_TIMEOUT_MS | No | Request timeout, default 30000 | 30000 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/linuskang/nginx-proxy-manager-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server