Dart LSP MCP
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 |
|---|---|
| get_diagnosticsA | Get Dart diagnostics for a project or specific file. Args: project_path: Absolute path to the Dart project root. file_path: Optional specific file to check (returns all if omitted). min_severity: Minimum severity level (error, warning, info, hint). ignore_unused_underscore: Filter out unused _xxx variable hints (default: True). Returns: Formatted string of diagnostics. |
| find_referencesA | Find all references to a symbol at a specific position. Args: project_path: Absolute path to the Dart project root. file_path: Absolute path to the Dart file. line: 0-indexed line number. column: 0-indexed column number. Returns: Formatted list of reference locations or error message. |
| get_capabilitiesA | Get LSP server capabilities for a project. Args: project_path: Absolute path to the Dart project root. Returns: JSON string of server capabilities. |
| go_to_definitionA | Go to definition of symbol at position. Args: project_path: Absolute path to Dart project root. file_path: Absolute path to Dart file. line: 0-indexed line number. column: 0-indexed column number. Returns: Definition location(s) or error message. |
| get_hoverA | Get hover information (documentation, type) for symbol. Args: project_path: Absolute path to Dart project root. file_path: Absolute path to Dart file. line: 0-indexed line number. column: 0-indexed column number. Returns: Hover content or error message. |
| get_document_symbolsA | Get all symbols (classes, functions, variables) in a Dart file. Args: project_path: Absolute path to Dart project root. file_path: Absolute path to Dart file. Returns: Hierarchical list of symbols or error message. |
| search_symbolsB | Search for symbols across the workspace. Args: project_path: Absolute path to Dart project root. query: Search query (partial name match). Returns: List of matching symbols with locations. |
| reindexA | Re-scan the workspace and index new or removed Dart files. Call this after creating, deleting, or renaming Dart files so the LSP server becomes aware of the changes. Args: project_path: Absolute path to the Dart project root. Returns: Summary of files added, removed, and total. |
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
Each tool covers a distinct LSP functionality (references, capabilities, diagnostics, symbols, hover, definition, reindex, symbol search). No two tools have overlapping purposes.
Most tools use a verb_noun pattern with snake_case (e.g., get_capabilities, find_references). However, 'reindex' is a single verb and 'go_to_definition' uses 'go_to' instead of a more common verb like 'get', causing slight inconsistency.
8 tools is an appropriate number for a Dart LSP server, covering essential navigation and analysis features without being excessive or deficient.
The tool surface includes core navigation (references, definition, hover, symbols) and diagnostics, but lacks common LSP features like code completion, formatting, rename, and code actions, leaving notable gaps.