citio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CITIO_CONFIG | No | Path to the config file | citio.yaml |
| CITIO_MEMORY | No | Memory/audit path | /memory |
| CITIO_WORKSPACE | No | Workspace path | /workspace |
| CITIO_CONFIG_B64 | No | Base64-encoded config (used by ECS, no file mount) |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| investigate_codebaseB | Search the codebase for files, functions, or patterns related to a query |
| read_fileB | Read file contents from the workspace |
| write_file | Write content to a file (creates or overwrites) |
| create_branchB | Create a git branch with an isolated worktree |
| create_prB | Push branch and create a GitHub pull request |
| run_commandB | Run an allowlisted command in the workspace |
| check_ci_statusB | Check CI/CD status of a pull request |
| save_findingC | Save a finding to organizational memory for future reference |
| recall_contextC | Recall prior findings from organizational memory |
| query_logsC | Query CloudWatch logs for recent events |
| post_updateB | Record a short progress update for the current task |
| query_audit_logC | Query the recorded MCP tool audit trail |
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 11 tools
Each tool targets a distinct action and resource: code search versus file read, branch creation versus PR creation versus CI status, findings versus progress updates, and CloudWatch logs versus audit logs. No two tools have overlapping responsibilities, and the descriptions make the boundaries clear.
All tool names follow a consistent verb_noun snake_case pattern, such as create_branch, query_logs, and save_finding. Verbs vary by purpose but remain predictable, and there is no mixing of casing or naming styles.
11 tools is a well-scoped size for a development and observability assistant. Each tool addresses a distinct stage of the workflow without redundancy, staying comfortably within the ideal range.
The set covers the main lifecycle: exploring code, running commands, creating branches and PRs, checking CI, saving and recalling findings, and querying logs and audit trails. Minor gaps such as PR merge/update or direct file editing are absent, but they are either workaroundable or intentionally left to external processes.