list_filesLABSCO SUMMARY
The editor's own knowledge, not a re-implementation.
Everything an agent asks for here is answered by VS Code itself — the same diagnostics you see underlined, the same git state, the same debug session. The premium tier is where that gets interesting: hover types, references and call hierarchy come from the language server that already understands the project, which is exactly what a file-reading agent has to guess at.
What it is
A VS Code extension that runs an MCP server inside the editor, so an agent works through VS Code instead of around it. The free half spans files, editing, terminal, diagnostics, debug, git, selection, diff, tasks, notifications, settings, refactor, snippets, testing and tab layout. The premium half exposes the Language Server Protocol providers — the data behind IntelliSense.
What you get
- Files: list, find, search, read, create, copy, move and delete, plus replacing lines, inserting text and undo —
list_files,read_file - Debugging as a first-class surface: sessions, breakpoints, stepping, variables and the call stack
- Git without leaving the conversation: status, diff, log, blame, commit, branch and stash
- Testing: run tests, read results and coverage
- The editor's own state — focus, workspace info, output channels and VS Code commands — plus errors, warnings and editor state
- Premium, licence required: completion at a position, hover docs and types, signature help, quick fixes and CodeLens, go-to-definition, references and call hierarchy, document and workspace symbols, formatting and rename, semantic tokens and inlay hints —
execute_hover - Categories switched on and off at runtime, with the client told to refresh its tool list —
manage_tool_categories
Requirements
VS Code 1.85.0 or later. Install the extension from the VS Code Marketplace; the server starts automatically on port 3002. Point any client that speaks Streamable HTTP at http://localhost:3002/mcp. Four settings cover the rest — maestroMcp.port, maestroMcp.host (default 127.0.0.1), maestroMcp.autoStart and maestroMcp.licenseKey. The LSP category needs a one-time licence key; everything else is free.
Setup effort
Follow the published steps — Install this extension from the VS Code Marketplace
USE CASES
01
Fixing what the editor already flagged
Read the current errors and warnings, open the file, and replace the offending lines.
02
Debugging with the agent watching
Set a breakpoint, step through, and read variables and the call stack as the session runs.
03
Preparing a commit
Read status and diff, then commit on a branch through the editor's own git integration.
04
Understanding a symbol properly
Ask the language server for hover types, definitions and references instead of grepping for the name.
05
Trimming the tool list
Turn categories on and off at runtime so the client only carries what this task needs.
4 tools
Listed in project docs. Your client may show a different list.
read_fileexecute_hovermanage_tool_categoriesBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
Install this extension from the VS Code Marketplace
The MCP server starts automatically on port 3002
Connect your MCP client to http://localhost:3002/mcp using the HTTP config block under MCP Clients (adjust the port if you changed maestroMcp.port)
Start using tools — list_files, read_file, execute_hover, etc.
Premium LSP tools only: run Maestro MCP: Enter License Key (or set maestroMcp.licenseKey) after buying a license.
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"maestro-mcp": {
"type": "http",
"url": "http://localhost:3002/mcp"
}
}
}
