ramen-mcp-bridge
by bkraad47
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAMEN_MCP_KEY | No | Ramen MCP key (rmk_…). Can also be provided via RAMEN_BRIDGE_KEY. | |
| RAMEN_BRIDGE_CA | No | Path to CA certificate file for self-signed fallback. | |
| RAMEN_BRIDGE_KEY | No | Alternative to RAMEN_MCP_KEY for the Ramen MCP key. | |
| RAMEN_BRIDGE_TLS | No | Set to 1 to enable TLS (verifies against system CA trust store). | |
| RAMEN_BRIDGE_ZONE | Yes | Zone name, e.g. local or a | |
| RAMEN_BRIDGE_GROUP | Yes | Group name, e.g. demo | |
| RAMEN_BRIDGE_TARGET | Yes | Target address of the Ramen worker or load balancer, e.g. localhost:8080 or <public-hostname>:443 | |
| RAMEN_BRIDGE_INSECURE | No | Set to 1 for plaintext/no TLS (for local worker). |
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
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 | |
This server cannot be deployed
Maintenance
ActivityNo data
ResponsivenessNo issues