Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NOTION_TOKENNoNotion token to enable Notion as a data source.
SUPABASE_KEYNoSupabase key to enable Supabase as a data source.
SUPABASE_URLNoSupabase URL to enable Supabase as a data source.
NEXUS_DEMO_MODENoSet to true to enable demo mode with fake sources (wiki and ticket tracker). No credentials are needed.
NEXUS_ALLOW_WRITESNoSet to true to unlock write tools (disabled by default).
NEXUS_ALLOW_DELETESNoSet to true to unlock delete tools (disabled by default).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Nexus exposes the user's Notion and Supabase data. Call server_info first to see which sources are connected and whether writes are enabled. Prefer read/search tools; write and delete tools are disabled unless the operator enabled them and always require confirmation.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
server_infoA

Describe this server: version, non-secret configuration (including whether writes/deletes are enabled) and the connected data sources. Call this first.

list_sourcesA

List the configured data sources and what each one supports.

health_checkA

Probe every data source concurrently and report status and latency.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation4/5

health_check is clearly distinct (concurrent probing with latency), but server_info and list_sources both surface information about connected data sources, creating a potential misselection point. Descriptions mitigate this by framing server_info as config/version/write-flags and list_sources as per-source capabilities.

Naming Consistency4/5

All names are readable two-word snake_case, but two are noun-first (server_info, health_check) while one is verb-first (list_sources). Minor deviation from a single predictable pattern, not enough to cause confusion.

Tool Count3/5

Three tools is thin even for a metadata/diagnostics server; server_info and list_sources could plausibly be merged. Each tool still has a defensible purpose, so it is borderline rather than mismatched.

Completeness2/5

The surface stops at introspection: there is no tool to actually query or interact with the configured data sources, and no tool to inspect individual source capabilities or configuration in depth beyond a list. An agent that needs data (not just status) hits a dead end.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues