Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {
    "mimeTypes": [
      "text/html;profile=mcp-app"
    ]
  }
}

Tools

Functions exposed to the LLM to take actions

NameDescription
project_listA

List local Work Plan projects with task progress counts, active chats, and workspace folder.

project_createB

Create a new Work Plan project and optionally seed tasks from a local Markdown plan, folder subdirectories, or GitHub issue URL.

project_getB

Read the project task tree, ready/waiting status, active sibling chats/files, upstream handoff_notes, and pinned notes.

task_planA

Idempotently create, update, or reorganize recursive tasks (task_id?, title, brief, files, target_tests, children) and depends_on edges ([upstream, downstream]).

task_startA

Start working on a task in this conversation: marks IN_PROGRESS, binds the conversation, and returns brief, upstream handoff_notes, active-file warnings, and optional git worktree command.

task_updateC

Advance task status (TODO, IN_PROGRESS, BLOCKED, IN_REVIEW, DONE, CANCELLED), attach concise handoff_notes for downstream chats, or record optional branch/PR metadata.

note_saveA

Save or update a project-scoped working note (decision, gotcha, spec, or note) persisted across conversations for this project.

note_listA

Search or filter working notes for a project (pinned and task-scoped notes ranked first).

memory_saveC

Save or idempotently update a durable cross-session project memory (architecture, convention, command, constraint, pitfall, context, or fact).

memory_listC

Search or filter durable project memories (always-injected and confirmed entries ranked first).

memory_deleteC

Delete a project memory entry by memory_id or key.

open_work_planC

Open the interactive Work Plan task tree, dependency graph, and notes board.

ui_get_stateC

App-only: fetch full UI snapshot for projects and active project.

ui_select_projectC

App-only: switch active project in the UI.

ui_bind_conversationC

App-only: pre-bind a newly launched conversationId to a task.

ui_create_projectC

App-only: create a new project from the UI modal.

ui_update_projectC

App-only: rename, pin, update project workspace/source, or configure/sync Knowledge Pack (KP).

ui_archive_projectC

App-only: archive or unarchive a project.

ui_delete_projectC

App-only: permanently delete a project.

ui_create_taskB

App-only: create a task or sub-task from the UI.

ui_update_taskC

App-only: update task fields, status, manual_status, or handoff_notes.

ui_move_taskC

App-only: reparent or reorder a task.

ui_delete_taskB

App-only: delete a task (and optionally its subtree).

ui_set_depC

App-only: add or remove a dependency edge between tasks.

ui_save_noteC

App-only: create or update a project/task note from the UI.

ui_delete_noteC

App-only: delete a project note.

ui_save_memoryC

App-only: create or update a project memory entry from the UI.

ui_delete_memoryC

App-only: delete a project memory entry from the UI.

ui_clear_active_editC

App-only: clear a stale active-edit lock row.

ui_browse_dirC

App-only: browse local directories and files for the UI path picker.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Work PlanInteractive task tree, dependency graph, and notes board

TDQS

C2.6/5.0

Scored across 30 tools

Disambiguation2/5

The set is split into a core agent-facing API and a parallel `ui_*` app-facing API that duplicates much of it: `ui_create_task` vs `task_plan`, `ui_update_task` vs `task_update`, `ui_save_note` vs `note_save`, `ui_save_memory` vs `memory_save`, and `ui_delete_memory` vs `memory_delete`. The 'App-only' labels help somewhat, but an agent still faces several near-identical operations and must infer which layer to use.

Naming Consistency3/5

All names are snake_case and resource-prefixed, but the convention shifts between noun_verb (`project_list`, `task_start`, `note_save`, `memory_delete`) and `ui_` + verb_noun (`ui_move_task`, `ui_delete_project`). The `ui_` prefix is consistently applied to app-only tools, which keeps it readable despite the mixed verb placement.

Tool Count2/5

30 tools is heavy for a project/task planning server, and roughly half are `ui_*` wrappers duplicating core operations. The effective agent-facing surface is around 15 tools, so many entries do not earn independent places in the set.

Completeness3/5

Core lifecycle is covered for projects (list/get/create), tasks (plan/start/update), notes (save/list), and memory (save/list/delete), plus an open-UI tool. However, project update/archive/delete, task deletion, and note deletion exist only as App-only tools, and there is no core task get/delete, leaving notable gaps for agent-driven workflows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues