MCPGate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (Railway sets this automatically) | 3000 |
| LOG_LEVEL | No | debug / info / warn / error | info |
| DATABASE_URL | No | PostgreSQL connection string (enables persistent audit trail) | |
| MCPGATE_CONFIG | No | Base64-encoded YAML config (for Railway/Docker) | |
| MCPGATE_AUTH_TOKEN | No | Bearer token for HTTP auth (reference in YAML via ${MCPGATE_AUTH_TOKEN}) |
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
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/martin-santiago/mcpgate'
If you have feedback or need assistance with the MCP directory API, please join our Discord server