nyyon-planner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_dayA | START HERE. One call returns: the planning brief (how to run the conversation), today's date, any existing plan for the day, this week's objectives, and the open items from recent days (the carry-over feed). Follow the brief, then save_plan. |
| read_planA | Read one day's saved plan (schedule + to-dos + what's still open). date default today. |
| save_planB | Write (or replace) a day's plan. schedule = time blocks; mark each ~2h Focus Session focus:true with ONE concrete deliverable. todos with star:true for the critical few. mode "strategic" (aligned to the week — set weekly_ref to the week anchor) or "wing_it". |
| update_planA | Edit a plan during the day — mark blocks/to-dos done, add items, reshuffle. Pass ONLY the keys you are changing; everything else is kept. |
| list_recent_plansA | The most recent PAST day plans with their open (unfinished) items — the carry-over feed. Surface these at the start of planning and ask: done, carry over, or drop? |
| search_plansA | Full-text search across all saved day plans (summaries, blocks, to-dos). Empty query = most recent. |
| read_weekB | The strategic layer: this week's 2-4 objectives (or a given week anchor date). Strategic days align to these. |
| set_weekB | Set the week's 2-4 strategic objectives (short outcome statements, or {text, done}). week_start default = the current week's anchor. |
| render_planA | Draw a day's plan as a clean 1080x1350 PNG (Focus Sessions accented, done items struck, the week's objectives at the foot). Returns the file path — show the image inline. Great for sharing the day or pinning it somewhere visible. |
| open_panelA | Start a local web panel for the day (loopback-only, token-guarded URL): REAL checkboxes for blocks, to-dos and objectives, plus a note box. Every interaction writes to the plan store and is reported back as panel_activity on the next plan_day call. Give the user the returned URL to open (or open it for them). |
| review_periodA | Follow-up analytics across saved plans: per-day rollups, completion rates (focus sessions, blocks, to-dos, starred), the SLIPPAGE list (items that appeared on multiple days before resolving — and the ones still stuck), and every touched week's objectives. Defaults to the last 7 days; pass from/to for a month or any range. The result includes a review_brief telling you how to narrate it — follow it. |
| get_settingsB | The active configuration: data directory, work week (days, anchor, timezone), and day-card theme. All overridable via NYYON_PLANNER_* env vars. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LevNyyon/nyyon-planner'
If you have feedback or need assistance with the MCP directory API, please join our Discord server