CodeFlow 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingB | Simple ping tool to echo a message and report analysis status. |
| semantic_searchB | Perform semantic search in codebase using vector similarity. |
| get_call_graphC | Export the call graph in specified format. |
| get_function_metadataB | Retrieve metadata for a specific function by its fully qualified name. Args: fqn: The fully qualified name of the function to retrieve metadata for. Returns: MetadataResponse containing detailed function metadata. |
| query_entry_pointsB | Retrieve identified entry points in the codebase with optional pagination and detail level. |
| impact_analysisD | – |
| generate_mermaid_graphB | Generate a Mermaid diagram for the call graph. |
| cleanup_stale_referencesA | Manually trigger cleanup of stale file references in the vector store. Removes documents that reference files that no longer exist on the filesystem. |
| reinforce_memoryD | – |
| query_memoryD | – |
| list_memoryD | – |
| forget_memoryD | – |
| check_driftB | Run drift detection on the current analyzed codebase. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| cortex-memory-top | Top Cortex memory entries for quick context. |
TDQS
Scored across 13 tools
Several tools have overlapping purposes (e.g., get_call_graph vs. generate_mermaid_graph, and multiple memory tools with no descriptions), making it harder for an agent to distinguish them without additional context.
Most tools follow a consistent verb_noun pattern with underscore separators, but a few (e.g., semantic_search, impact_analysis) deviate slightly, preventing a perfect score.
With 13 tools, the set is reasonably scoped for a code analysis server, neither too sparse nor too heavy, though some tools may be redundant.
Missing descriptions for several tools (e.g., forget_memory, impact_analysis) and apparent gaps like no tool for listing functions or retrieving source code suggest the surface is incomplete for comprehensive code analysis.