Zenith MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | Yes | Your Supabase project URL | |
| SUPABASE_SERVICE_KEY | Yes | Your Supabase service role key (secret) |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| log_habitB | Mark a habit as completed for today. |
| get_today_statusA | Returns a full dashboard of which habits are done/not done today, today's pull-up GtG total reps, and mission day progress. |
| get_streakA | Returns the current consecutive-day streak for a specific habit. |
| get_mission_overviewA | Returns a full 90-day mission progress overview:
|
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 4 tools
Each tool serves a clearly distinct purpose: logging a completion, viewing today's dashboard, checking a specific habit's streak, and viewing overall mission progress. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: log_habit, get_today_status, get_streak, get_mission_overview. The verbs are consistent ('log' and 'get'), and the nouns clearly describe the target.
With 4 tools, the set is concise and well-scoped for a habit-tracking mission server. Each tool covers a necessary interaction (log and three read views), and the count is within the ideal range.
The server covers core logging and status views, but lacks a way to list available habits or manage them (create/update/delete). An agent cannot discover valid habit names, which could cause failures when calling log_habit or get_streak.