context-compose
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initA | Initialize Context Compose project (copy assets directory to .contextcompose). You must specify the project root directory with the projectRoot parameter. |
| start-contextA | Start a new context for a task. Reads -context.yaml file from the assets directory. Combines prompts from all referenced files (personas, rules, mcps, actions) to provide context for AI development. |
| validate-contextB | Validate a context file and its referenced component files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: project initialization, context starting, and validation. No overlapping functionality.
Two tools use hyphenated verb-noun ('start-context', 'validate-context') while 'init' is a single verb, but the pattern is clear and predictable.
Three tools are well-scoped for a context management tool, covering setup, usage, and validation without redundancy.
Core operations are covered (init, start, validate), but missing potential lifecycle operations like listing or deleting contexts, though not critical for basic use.