mcp-oauth-starter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host interface to bind the server to. Defaults to 127.0.0.1. | 127.0.0.1 |
| PORT | No | Port to bind the server to. Defaults to 8000. | 8000 |
| MCP_JWKS_URL | Yes | Usually `jwks_uri` from `{issuer}/.well-known/oauth-authorization-server`. Keys are cached and refetched on an unknown `kid`. | |
| MCP_ALGORITHMS | No | Optional. JWT algorithms to accept. Defaults to RS256. `none` is refused at construction. | RS256 |
| MCP_AUTH_ISSUER | Yes | Issuer identifier of your authorization server. Must equal the `iss` claim byte-for-byte. | |
| MCP_RESOURCE_URL | Yes | The canonical URI of this server (RFC 8707 §2), exactly as clients send it in `resource`. Must be https, no fragment, no trailing slash. | |
| MCP_REQUIRED_SCOPES | No | Optional. Space-separated scopes required for the whole server. Advertised as `scopes_supported` and in the challenge. |
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