Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CPC_KNOWLEDGE_BASENoSet to a custom KnowledgeBase directory (useful if the clone is public and your project JSON should stay private).

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_desk_summaryA

Use this first. Compact desk under 800 tokens. Done cards older than the archive window are left out of the list. The archived count is still reported. Pass includeArchived to list those cards. Skip list_projects unless the user asks for a deep dive.

list_projectsB

Full project roster. Prefer get_desk_summary first. Use this for a deep dive only.

get_project_statusA

Full detail for one project, including notes and cards. Archived done cards are omitted from the card list. The archived count is still reported. Pass includeArchived to list them. Prefer get_desk_summary first.

search_deskA

Search notes, card titles, kinds, and KnowledgeBase markdown. Archived done cards are included and marked archived. Prefer get_desk_summary first.

search_code_patternsA

Deprecated alias of search_desk. Prefer search_desk. Use get_desk_summary first.

add_projectA

Manually register a project. Path is optional for non-coding work. Coding projects need a folder. Prefer register_from_workspace when an agent is already in a repo.

update_project_statusA

Update status or notes for a project. Prefer get_desk_summary first.

get_project_timelineB

Status timeline for one project. Prefer get_desk_summary first.

get_activity_heatmapC

Activity heat map for recent days. Scores and event counts. Prefer get_desk_summary first.

get_technology_trendsA

Framework usage, emerging tags, and adoption timeline for coding projects. Prefer get_desk_summary first.

get_project_healthB

0-100 health scores with factors and recommendations. Prefer get_desk_summary and the Analytics tab.

open_deskB

Write KnowledgeBase/desk/index.html and return its path. Open the file from disk.

add_cardB

Add a Kanban card. Optional memoryRef is an opaque id. DPC never copies memory prose.

move_cardA

Move a card to another column, then regenerate the desk page. Leaving done brings an archived card back onto the board.

update_cardB

Update card title, column, or memoryRef. Leaving done, or any edit that refreshes updated, brings an archived card back onto the board.

rename_columnB

Rename a Kanban column. Cards in that column follow the new name.

register_from_workspaceA

Silently register or update a coding project from the agent's working directory and git remote. Never creates folders.

file_under_projectC

Find the closest existing non-coding project or create one with no path. Reply includes Filed under new/existing project.

rename_projectC

Rename a project after a wrong guess.

merge_projectsA

Merge a duplicate project into another. Cards move to the target.

start_desk_serverA

Opt-in localhost Kanban server bound to 127.0.0.1 on a fixed port (default 47821). Returns a bookmark URL with no token plus a one-time sign-in URL (valid once, for 10 minutes). Calling again while running mints a new sign-in code without rotating the write token. Token file mode 0600. Static index.html still works without it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 21 tools

Disambiguation3/5

Most tools have recognizable distinct purposes, but there is meaningful overlap among the summary/detail/analytics tools: get_desk_summary, list_projects, get_project_status, and the various project analytics tools all read related project data. Project creation is split across add_project, register_from_workspace, and file_under_project, and search_code_patterns is explicitly a deprecated alias of search_desk, which creates avoidable confusion.

Naming Consistency5/5

Tool names consistently use snake_case with a verb_noun or verb_object pattern, such as get_desk_summary, add_card, move_card, rename_project, and merge_projects. The convention is predictable throughout the set, with only benign variations like file_under_project and start_desk_server.

Tool Count3/5

Twenty-one tools is on the heavy side for a project/desk coordinator, especially because several tools cover closely related summary and analytics views. The deprecated search alias and the repeated 'prefer get_desk_summary first' guidance suggest some tools do not fully earn their place.

Completeness3/5

The server covers project registration, status updates, Kanban card creation/movement/update, search, analytics, and desk serving. However, lifecycle coverage is incomplete: there is no delete_project, delete_card, or column creation/deletion, and card operations rely on summaries rather than a dedicated get_card tool.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues