Conector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONECTOR_HOST | No | Interface to bind. Use `0.0.0.0` only behind a firewall or reverse proxy. | 127.0.0.1 |
| CONECTOR_HSTS | No | With an `https://` public URL, send Strict-Transport-Security. Set `0` if the same host name also serves plain-HTTP services on other ports. | 1 |
| CONECTOR_PORT | No | Port to listen on. | 8790 |
| CONECTOR_DATA_DIR | No | Users, tokens, encrypted credentials, the master key and the audit log. | ./data |
| CONECTOR_PUBLIC_URL | No | Address that people and agents use. Some OAuth providers require `https://`. | http://localhost:<port> |
| CONECTOR_TRUST_PROXY | No | `1` behind a reverse proxy on the same machine or private network. | |
| CONECTOR_ALLOWED_HOSTS | No | Extra `Host` headers to accept, comma-separated (for example `conector.lan:8790`). | |
| CONECTOR_SESSION_HOURS | No | Idle time before panel sessions expire. Sessions also end when the server restarts. | 12 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| conector_appsA | List the apps this Conector token can use, with their tools, and the panel address where the user connects more apps. |
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 1 tool
Only one tool exists, so there is no risk of selecting the wrong tool. Its purpose is clearly stated and distinct.
With a single tool named conector_apps, there is no inconsistency to assess. It uses snake_case and is readable.
A single tool is borderline thin for a server named Conector that implies broader app connection capabilities. It may be sufficient for discovery, but 1 tool is low.
The surface only lists apps and their tools, with no way to actually invoke or manage those app tools. This leaves a significant gap for an integration/connector server.