Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DATABASE_URLYesYour Supabase connection string

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

Tools

Functions exposed to the LLM to take actions

NameDescription
get_project_infoA

Returns information about the current project including name, status, and description

create_taskA

Creates a new task with title, description, status (backlog|todo|in_progress|done), dependencies, assignee, priority, and tags. ⚠️ IMPORTANT: The tool response includes automatic workflow guidance (nextSteps field) for analyzing the task before implementation. Always follow the nextSteps instructions to ensure complete metadata and dependency mapping.

list_tasksA

Lists all tasks, optionally filtered by status and/or category

update_taskA

Updates an existing task. Validates status transitions and dependencies

delete_taskA

Deletes a task. Checks for dependent tasks and prevents deletion if other tasks depend on it. Invalidates caches automatically.

get_task_contextA

Gets comprehensive context for a task including dependencies, previous work, guidelines, and tech stack

get_execution_orderB

Calculates the topological execution order for tasks based on dependencies. Uses Kahn's algorithm to detect circular dependencies and return tasks sorted by execution sequence. Handles edge cases: cycles (returns error with cycle path), multiple dependency chains (ensures all paths considered), and isolated tasks (included at end).

list_templatesC

Lists available prompt and code templates

list_patternsC

Lists coding patterns learned from the codebase

list_learningsB

Lists learnings from past experiences

render_templateB

Renders a template with provided variables

get_relevant_knowledgeC

Gets relevant templates, patterns, and learnings for a task

intelligent_decompose_storyA

🚀 INTELLIGENT WORKFLOW: Generates a structured prompt for Claude Code to analyze the codebase and decompose a user story based on REAL project context. Claude Code will use Grep/Glob/Read to explore the codebase before creating tasks. Returns a prompt with instructions for Claude Code to follow.

save_story_decompositionA

Saves the decomposition analysis performed by Claude Code after exploring the codebase. Call this after intelligent_decompose_story once you've analyzed the codebase and created the task breakdown with real file paths and dependencies.

add_feedbackA

Add feedback/learning from task execution to improve future recommendations

get_similar_learningsC

Find similar learnings/feedback based on context and pattern matching

get_top_patternsB

Get the most frequently used patterns across all tasks, sorted by frequency and recency

get_trending_patternsA

Get patterns that are trending (most used in recent days), useful for identifying current development patterns

get_pattern_statsA

Get detailed statistics for a specific pattern including frequency, success rate, and usage timeline

detect_failure_patternsA

Automatically detect patterns with high failure rates to identify risky approaches. Returns patterns sorted by failure rate with risk assessments and recommendations.

check_pattern_riskA

Check if a specific pattern has a history of failures and get risk assessment before using it. Provides immediate feedback on pattern safety.

prepare_task_for_executionA

Prepares a task for execution by generating a structured analysis request. Returns a prompt that guides Claude Code to analyze the codebase using its tools (Read, Grep, Glob). ⚠️ IMPORTANT: The response includes workflowInstructions field - follow it to know exactly what to do next. After analysis, call save_task_analysis with the results.

save_task_analysisA

Saves the codebase analysis performed by Claude Code. Call this after analyzing the codebase following the prepare_task_for_execution prompt. Records dependencies, risks, and recommendations. ⚠️ IMPORTANT: The response includes nextSteps guidance - follow it to get the enriched execution prompt with all context.

get_execution_promptA

Generates an enriched execution prompt with full context for implementing a task. Call this after save_task_analysis to get a comprehensive prompt with dependencies, risks, patterns, and guidelines. ⚠️ IMPORTANT: The response includes nextSteps for implementation - follow the prompt and update task status to in_progress when you start.

save_dependenciesB

Save analyzed dependencies and detect potential conflicts with other tasks

get_task_dependency_graphB

Get the dependency graph (nodes and edges) for a specific task

get_resource_usageB

Get all tasks that touch a specific resource

get_task_conflictsA

Get potential conflicts for a task based on resource usage

get_user_storiesA

Get all user stories with task counts for dashboard display

get_tasks_by_user_storyB

Get all tasks belonging to a specific user story

safe_delete_tasks_by_statusA

Safely delete tasks by status, automatically preserving user stories with completed work and tasks with dependencies. Returns detailed report of what was deleted vs. preserved.

get_user_story_healthA

Get health monitoring data for all user stories, showing current vs. suggested status, completion percentage, and safety flags for deletion

delete_user_storyA

Delete a user story and all its sub-tasks. Checks for completed work and external dependencies. Use force=true to delete user stories with completed sub-tasks.

get_project_configurationB

Get the complete configuration for a project including tech stack, sub-agents, MCP tools, guidelines, and code patterns

initialize_project_configurationC

Initialize default configuration for a project including tools and guardian agents

add_tech_stackC

Add a technology stack entry to the project configuration

update_tech_stackC

Update an existing tech stack entry

remove_tech_stackA

Remove a tech stack entry from the project

add_sub_agentC

Add a sub-agent (guardian) to the project configuration

update_sub_agentC

Update an existing sub-agent configuration

add_mcp_toolC

Add an MCP tool configuration to the project

update_mcp_toolC

Update an existing MCP tool configuration

add_guidelineB

Add a project guideline or coding standard

add_code_patternB

Add a reusable code pattern to the project library

read_claude_code_agentsB

Read and parse Claude Code agents from .claude/agents/ directory

sync_claude_code_agentsA

Synchronize Claude Code agents to Orchestro database. Reads agents from .claude/agents/, parses YAML frontmatter and prompts, then upserts to sub_agents table

suggest_agents_for_taskA

Get AI-powered agent suggestions for a task based on description and category. Returns top 3 most relevant agents with confidence scores

suggest_tools_for_taskA

Get AI-powered MCP tool suggestions for a task based on description and category. Returns top 3 most relevant tools with confidence scores

update_agent_prompt_templatesB

Update prompt templates for all agent types with predefined best-practice templates

get_task_historyA

Get complete event history for a task including all status changes, decisions, code changes, and guardian interventions

get_status_historyB

Get status transition history for a task

get_decisionsA

Get all decisions made for a task

get_guardian_interventionsA

Get all guardian interventions for a task

get_code_changesB

Get all code changes for a task

record_decisionB

Record a decision made during task execution

record_code_changeB

Record a code change made during task execution

record_guardian_interventionB

Record a guardian intervention during task execution

record_status_transitionB

Record a status transition for a task

get_iteration_countC

Get the number of iterations (updates) for a task

get_task_snapshotB

Get a snapshot of a task at a specific point in time

rollback_taskB

Rollback a task to a previous state at a specific timestamp

get_task_statsB

Get aggregated statistics for a task including event counts and timeline

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/khaoss85/mcp-orchestro'

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