skgate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TZ | No | Time zone for the UI and logs, for example `America/New_York`. | UTC |
| PGID | No | Run-as id; never `0`. | 1000 |
| PUID | No | Run-as id; never `0`. | 1000 |
| DB_PATH | No | SQLite file. | /data/skgate.db |
| LOG_LEVEL | No | `info` or `debug`. | info |
| PUBLIC_URL | No | Public origin, no trailing slash. | http://localhost:8080 |
| LISTEN_ADDR | No | Listen address. | :8080 |
| MANAGED_DIR | No | Work dirs and clones of managed upstreams. | /data/managed |
| OIDC_ISSUER | Yes | Issuer URL, equal to the provider's discovery `issuer`. | |
| OIDC_SCOPES | No | Requested scopes. | openid profile email groups |
| SECRETS_KEY | No | Encrypts stored upstream secrets. 32-byte base64 or a passphrase. | random `secrets.key` file |
| GITHUB_TOKEN | No | Optional GitHub token for **Suggest** when it reads a repository. An upstream's own access token takes precedence. Raises GitHub's rate limit. | |
| OIDC_CLIENT_ID | Yes | Confidential client ID. | |
| MANAGED_MAX_PROCS | No | Concurrent managed processes; `0` is unlimited. | 0 |
| OIDC_REDIRECT_URL | No | Callback registered at the provider. | PUBLIC_URL/admin/oidc/callback |
| OIDC_CLIENT_SECRET | Yes | Confidential client secret. | |
| OIDC_ALLOWED_EMAILS | No | Comma list limiting who is admin. | |
| OIDC_ALLOWED_GROUPS | No | Comma list limiting who is admin. | |
| MCP_OAUTH_REQUIRE_CONSENT | No | Approve/Deny page after login at `/authorize`. | true |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aboutA | Describe skgate: what it is, the running version, the edition, the licence and where its source and docs live. Takes no arguments. Returns one object with name, version, edition, summary, license, repository, docs and mode. Read-only and offline: it answers from the binary alone and contacts nothing. Call it first to learn what skgate is before using list_features or config_help. |
| list_featuresA | List what skgate does, one entry per feature, optionally limited to one area. Takes an optional area: mcp (MCP servers and tools), openapi (REST APIs as tools), llm_proxy (the OpenAI-compatible API, providers, aliases and keys), auth (OAuth and sign-in) or deploy (running and configuring it). Without an area it returns every feature. Returns an object with the area asked for ('all' by default) and a features array of id, area and summary. An unknown area is an error that names the valid ones. Read-only and offline. |
| config_helpA | Explain the environment variables that configure a skgate server. Takes an optional variable, an exact variable name such as PUBLIC_URL (case does not matter); without it the tool returns every variable. Returns an object with a settings array of name, default and description, in the order of the README table. Defaults are the documented values and no secret is ever included. An unknown name is an error that lists the valid names. Read-only and offline: it shows documented defaults, reads no environment variable and cannot tell you the values of a running server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
All three tools are read-only introspection, but they target distinct surfaces: product metadata (about), feature inventory (list_features), and environment variables (config_help). 'about' and 'list_features' are the closest pair since about returns a summary and mode while list_features returns feature entries, but the descriptions draw a workable line and about is explicitly an entry point.
The names mix conventions: 'about' is a bare preposition/noun, 'list_features' is verb_noun, and 'config_help' is noun_noun. All are lowercase snake-ish and readable, but there is no predictable pattern an agent could extrapolate from.
Three tools is thin for a server whose whole purpose is explaining a product, though each is scoped to a different information source with no redundancy. It sits at the borderline rather than being clearly under- or over-provisioned.
The surface is deliberately offline and binary-only, so it cannot read live environment values, enumerate configured MCP servers/tools, or validate an actual running config. Documentation lookup is covered, but agents that need to inspect or verify a running skgate instance hit a dead end.