Ada 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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ada_goto_definitionB | Navigate to the definition of an Ada symbol at a given location |
| ada_hoverC | Get type information and documentation for an Ada symbol |
| ada_diagnosticsA | Get synchronized compiler diagnostics for one Ada file, or the explicitly incomplete cache of published diagnostics when no file is provided |
| ada_find_referencesB | Find all references to an Ada symbol across the project |
| ada_document_symbolsB | Get all symbols defined in an Ada file (outline) |
| ada_workspace_symbolsB | Search for symbols by name across the complete indexed Ada workspace |
| ada_type_definitionA | Navigate from an object or parameter identifier to its type declaration; use ada_goto_definition on an explicit type name |
| ada_implementationB | Navigate from declaration to implementation (spec to body) |
| ada_project_infoA | Select an exact GPR project with an optional per-view environment and return its evaluated structure; later file tools reuse the validated selection |
| ada_call_hierarchyB | Get call hierarchy (incoming/outgoing calls) for an Ada symbol |
| ada_dependency_graphB | Analyze package dependencies from 'with' clauses |
| ada_completionsC | Get code completion suggestions at a position in an Ada file |
| ada_signature_helpC | Get function/procedure signature help at a position |
| ada_code_actionsC | Get available code actions (quick fixes, refactorings) for a range |
| ada_rename_symbolC | Rename an Ada symbol across the entire project |
| ada_format_fileC | Format an Ada source file using GNATformat |
| ada_get_specB | Navigate from body to spec file, or find corresponding spec |
| ada_buildC | Build an Ada project using GPRbuild and return compilation results |
| ada_alire_infoB | Get Alire project information from alire.toml |
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 19 tools
Most tools map to clearly distinct LSP-style operations (hover, diagnostics, completions, rename, format, build). There is some potential confusion among the navigation family (ada_goto_definition, ada_type_definition, ada_implementation, ada_get_spec), but the descriptions explicitly clarify their different targets. ada_project_info and ada_alire_info are also somewhat adjacent, though their scopes differ.
All 19 tools share the ada_ prefix and consistent snake_case naming. The style is predictable, with clear action-oriented names (ada_goto_definition, ada_find_references, ada_rename_symbol) and conventional noun-style LSP terms (ada_hover, ada_completions, ada_diagnostics).
Nineteen tools is on the heavy side but appropriate for an Ada language-server integration covering navigation, symbols, completion, diagnostics, refactoring, formatting, build, and project metadata. The surface is broad but each tool has a distinct role.
The set covers the core language-server workflows: navigation, references, symbols, diagnostics, completion, code actions, rename, formatting, build, call hierarchy, dependency graph, and project info. Minor gaps remain around less central LSP features such as document highlights, selection range, semantic tokens, or code lens, but there are no major dead ends for typical Ada development tasks.