Skip to main content
Glama
quochuy
by quochuy

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COORDINATION_DIRNoAbsolute path to the shared coordination directory. Both clients must point to the same directory. If unset, defaults to the .ai/coordination directory relative to the current working directory.<cwd>/.ai/coordination

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_taskA

Create a new coordination task for an implementer (e.g. OpenCode) to pick up. Starts in status 'pending'.

list_tasksA

List coordination tasks, optionally filtered by status, assignee, creator, or tag. Returns a lightweight summary per task (no history[], plus a computed idleSeconds while claimed/in_progress) so repeated polling stays cheap — call get_task for the full record including history.

get_taskA

Fetch full details for a single task by id, including its status, version, and history.

search_tasksA

Full-text search over task titles, descriptions, and tags (case-insensitive substring match). Returns the same lightweight summary shape as list_tasks (no history[]) — call get_task for the full record.

claim_taskA

Claim a pending task as the implementer working on it. Fails if the task was pre-assigned to someone else. Returns the task summary (no history[] — call get_task for that).

claim_next_taskA

Atomically claim the first eligible pending task (optionally filtered by tag) instead of a separate list_tasks + claim_task round trip. Skips tasks pre-assigned to someone else. Returns null if no eligible pending task is available, otherwise a task summary (no history[] — call get_task for that).

complete_taskA

Mark a claimed/in-progress/revision-requested task as completed and ready for the creator to review. Returns the task summary (no history[] — call get_task for that).

cancel_taskA

Cancel a task that is not already completed/approved/cancelled. Returns the task summary (no history[] — call get_task for that).

reopen_taskA

Reopen a cancelled/completed/approved task back to pending, clearing its assignee and prior progress so it can be re-claimed. Returns the task summary (no history[] — call get_task for that).

approve_taskA

Approve a completed task (typically called by the creator/reviewer after checking the implementer's work). Returns the task summary (no history[] — call get_task for that).

request_revisionA

Send a completed task back to the implementer for changes. Posts the feedback as a message on the task's thread. Returns the task summary (no history[] — call get_task for that).

post_messageA

Post a message to a task's conversation thread (e.g. clarifications, review feedback, status notes).

get_messagesA

Fetch a task's conversation thread, optionally only messages after a given ISO timestamp.

update_progressA

Report progress (0-100, whole numbers) on a claimed/in-progress/revision-requested task. The first call in a claim or revision cycle automatically advances the task's status to 'in_progress'. Rejects tasks not currently open for work (pending, completed, approved, cancelled). Returns the current snapshot (no history[] — call get_progress for that).

get_progressA

Fetch the latest progress snapshot (and history) for a task. Returns null if no progress reported yet.

wait_for_taskA

Block (polling, lock-free) until a task's status changes, or until timeout_seconds elapses — use instead of repeatedly calling get_task in a loop. Without until_status, returns as soon as status differs from its value at call time; with until_status, waits specifically for that status. Timing out is a normal result (timed_out: true), not an error — re-call to keep waiting.

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/quochuy/ai-coord-mcp'

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