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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
project_createA

Create a new project. Projects are the top-level container for all work.

project_listA

List all projects with epic/task counts and completion percentages. Optionally filter by status.

project_updateA

Update a project. Pass only the fields you want to change. Set status to "archived" to soft-delete.

epic_createB

Create an epic within a project. Epics group related tasks into a feature or workstream.

epic_listB

List epics for a project with task counts and completion stats. Optionally filter by status or priority.

epic_updateA

Update an epic. Pass only the fields you want to change. Set status to "cancelled" to soft-delete.

task_createB

Create a task within an epic. Tasks are the primary unit of work.

task_listA

List tasks with optional filters. If no epic_id given, lists across ALL epics. Includes subtask counts and dependency info.

task_getA

Get a single task with full details including all subtasks, related notes, comments, and dependencies.

task_updateB

Update a task. Pass only fields to change. Status transitions are automatically logged in the activity log.

subtask_createB

Create one or more subtasks (checklist items) for a task. Accepts a single title string or an array of title strings for batch creation.

subtask_updateB

Update a subtask title, status, or sort order.

subtask_deleteA

Delete one or more subtasks. Accepts a single ID or array of IDs.

note_saveA

Create or update a note. Notes capture decisions, context, progress, meeting notes, blockers, technical details, or release info. If "id" is provided, updates the existing note; otherwise creates a new one.

note_listA

List notes with optional filters. Returns notes sorted by most recent first.

note_searchA

Search across note titles and content by keyword.

note_deleteA

Delete a note by ID.

comment_addA

Add a comment to a task. Comments create a chronological discussion thread — useful for leaving breadcrumbs across sessions.

comment_listB

List all comments on a task in chronological order.

template_createA

Create a reusable task template. Templates define a set of tasks that can be instantiated into any epic. Use {variable} placeholders for dynamic values.

template_listA

List all available task templates.

template_applyA

Apply a template to create tasks in an epic. Replaces {variable} placeholders with provided values.

template_deleteA

Delete a task template.

tracker_dashboardA

Get a comprehensive project overview in a single call. Returns: project info, all epics with task counts, overall stats (total/done/blocked/in_progress), recent activity, and recent notes. This is the best first tool to call when starting work on a project.

tracker_initA

Initialize the tracker for a project. If the database is empty, creates a project with the given name. If a project already exists, returns its info.

tracker_searchA

Search across ALL entities (projects, epics, tasks, notes) by keyword. Returns categorized results.

activity_logA

View the activity log showing what changed and when. Useful for understanding recent progress or reviewing what happened since the last session.

tracker_session_diffA

Show what changed since a given timestamp. Returns aggregated summary with counts by action and entity type, plus highlights of key changes. Call this at the start of a session to understand what happened since the last one.

task_batch_updateB

Update multiple tasks at once. Useful for changing status of several tasks (e.g., mark 3 tasks as done) or reassigning tasks.

tracker_exportA

Export a full project as nested JSON. Includes all epics, tasks, subtasks, comments, dependencies, and related notes. Useful for backup, migration, or sharing.

tracker_importA

Import a project from JSON (matching tracker_export format). Creates all entities with new IDs and remaps references. Uses a transaction for atomicity.

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/spranab/saga-mcp'

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