Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
backlog_listA

List tasks from backlog. Returns most recently updated items first. Default: shows only active work (open/in_progress/blocked), limited to 20 items. Use counts=true to check if more items exist beyond the limit.

backlog_getA

Get full details by ID. Accepts task IDs (TASK-0001, EPIC-0002) or MCP resource URIs (mcp://backlog/resources/design.md). Works for any item regardless of status.

backlog_createC

Create a new item in the backlog.

backlog_updateA

Update an existing item. For editing the markdown body, use write_resource with str_replace.

backlog_deleteA

Delete an item permanently.

backlog_searchA

Search across all backlog content — tasks, epics, and resources. Returns relevance-ranked results with match context. Use this for discovery; use backlog_list for filtering by status/type.

write_resourceA

Edit the markdown body of an existing task or epic. All entity creation goes through backlog_create.

  • The append command will add content to the end of the body, automatically adding a newline if needed. Notes for using the str_replace command:

  • The old_str parameter should match EXACTLY one or more consecutive lines from the original body. Be mindful of whitespaces!

  • If the old_str parameter is not unique in the body, the replacement will not be performed. Include enough context to make it unique.

  • The new_str parameter should contain the edited lines that should replace the old_str

backlog_wakeupA

Dense session-start briefing: active tasks, current epics, recent completions (with evidence snippets), and recent activity. No focal entity required — use this at the start of every session to understand what you were working on. Optional scope narrows to a folder (for project-scoped briefing), milestone, or epic.

backlog_recallA

Recall episodic memories — short digest records captured when tasks complete or artifacts are created. Distinct from backlog_search (which queries live entities). Use this to answer "what did I finish recently about X?" or "what artifacts live under FLDR-0001?" — the memories point back to entities via metadata.entity_id.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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/gkoreli/backlog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server