Aplomo MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aplomo_prepare_changeC | Prepare one coding request with repository structure, relevant existing patterns, and architecture rules in a single call. |
| aplomo_understand_repoB | Detect technologies and summarize modules and symbols in the repository. |
| aplomo_find_existing_patternsA | Search a bounded set of source files for existing implementations before adding an abstraction. |
| aplomo_validate_abstractionB | Require reuse or an explicit responsibility/lifecycle justification before adding an abstraction. |
| aplomo_review_planB | Check whether an implementation plan covers patterns, scope, compatibility, and validation. |
| aplomo_review_architectureA | Summarize architecture configuration and repository structure for an architecture review. |
| aplomo_review_diffA | Review the current git diff for risky size, secrets, and missing test changes. |
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 7 tools
Tools are mapped to distinct workflow phases (understanding, pattern search, change preparation, abstraction validation, plan/architecture/diff review), so misselection is unlikely. The only mild overlap is between understand_repo and review_architecture, which both involve summarizing repository structure.
All tools share the aplomo_ prefix and use a consistent verb_noun snake_case pattern (prepare_change, understand_repo, review_plan, etc.). The pattern makes the action of each tool predictable from its name.
Seven tools is a tight, well-scoped set for a code-review and change-preparation server. Each tool covers a distinct step without redundancy or bloat.
The set covers the full intended workflow: understanding the repo, finding existing patterns, preparing a change, validating abstractions, and reviewing the plan, architecture, and diff. No obvious dead ends or critical missing operations for the server's apparent review/preparation purpose.