Remote MCP Server Template
by romulorgc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Interface to bind. The Docker image sets `0.0.0.0`. | 127.0.0.1 |
| PORT | No | Port to listen on. | 3000 |
| PUBLIC_URL | Yes | Canonical origin of this server (scheme, host, optional port; no path). Published as the metadata `resource`. Required. | |
| AUTH_ISSUER | Yes | Issuer of your authorization server. https required, except localhost. Required. | |
| AUTH_AUDIENCE | No | Expected `aud` of access tokens. | PUBLIC_URL |
| AUTH_JWKS_URL | No | JWKS endpoint. Empty means discover it from the issuer metadata (OIDC discovery, then RFC 8414). | discovered |
| ALLOWED_ORIGINS | No | Comma-separated browser origins allowed to call the server. Empty refuses every request with an `Origin` header. | none |
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
ActivityMaintained
ResponsivenessNo issues