CodeLogic
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODELOGIC_MV_NAME | Yes | Your CodeLogic materialized view name | |
| CODELOGIC_PASSWORD | Yes | Your CodeLogic password | |
| CODELOGIC_USERNAME | Yes | Your CodeLogic username | |
| CODELOGIC_SERVER_HOST | Yes | URL to the CodeLogic server (e.g. https://myco.app.codelogic.com) |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codelogic-method-impactA | Analyze impacts of modifying a specific method within a given class or type. Uses CODELOGIC_WORKSPACE_NAME environment variable to determine the target workspace. Recommended workflow:
|
| codelogic-database-impactA | Analyze impacts between code and database entities. Uses CODELOGIC_WORKSPACE_NAME environment variable to determine the target workspace. Recommended workflow:
|
| codelogic-graph-capabilitiesA | Fetch graph API capabilities/manifest from the CodeLogic server (GET). Returns label and relationship metadata when the graph tier is deployed; otherwise explains missing routes. Uses CODELOGIC_WORKSPACE_NAME for MV id unless |
| codelogic-graph-searchB | Search the CodeLogic knowledge graph (curated HTTP API). Provide |
| codelogic-graph-impactC | Bounded graph impact from seed node ids (curated HTTP API). Optional |
| codelogic-graph-path-explainA | Explain bounded paths between two graph nodes (curated HTTP API). Requires |
| codelogic-graph-validate-change-scopeC | Validate whether a proposed change scope is safe given seed graph nodes (curated HTTP API). |
| codelogic-graph-ownersB | Look up owners/reviewers for a graph node (curated HTTP API). Provide |
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 8 tools
The tools are largely distinct: method-impact and database-impact target specific impact scenarios, while the graph-* tools handle search, traversal, path explanation, validation, and ownership lookup. There is minor potential confusion between graph-impact and graph-validate-change-scope since both analyze change effects, but their descriptions clarify different entry points.
All tools share a consistent codelogic- prefix and hyphenated convention, making the family recognizable. However, the second segment mixes styles: some are noun phrases (graph-capabilities, graph-owners) and others are verb-oriented (graph-search, graph-path-explain), so the pattern is not fully uniform.
Eight tools is well-scoped for a CodeLogic analysis server: two domain-specific impact analyzers, one general graph impact/search pair, plus metadata/owners lookups. Each tool covers a distinct capability without redundancy.
The surface covers the core workflows: impact analysis by method, database entity, and generic graph traversal, plus search, path explanation, ownership lookup, and capability discovery. This is a coherent analysis-focused API with lifecycle operations not needed for the domain.