Direct answer
Best MCP Servers for VS Code
The best MCP servers for VS Code are a short list picked by job: Zambo, added through the MCP config at https://zambo.dev/mcp, for broad tools, memory shared with your other AIs, and a verifiable receipt for agent work in the Copilot era, plus a code intelligence, docs, or issue tracking server only where your projects prove the need. VS Code makes adding servers easy, which is exactly why a chooser matters: this page keeps the list short and the receipts real.
Updated October 20, 2026.
How to choose: by job, not by extension count
VS Code culture runs on extensions, and MCP servers inherit the habit: there is always one more to try, and trying feels free. It is not free inside an agent session. Every server adds tool descriptions the model must carry, options it must weigh, and config you must keep alive across updates and machines. The developers who get the most from agent mode in VS Code run the fewest servers that cover their real jobs, and they can name each job out loud.
The real jobs, for most VS Code users, are four. Broad tools with memory and proof: the everyday capabilities plus a record of what the agent did. Code intelligence: fast symbol and reference work across a big repo. Documentation lookup: current docs for libraries that move faster than training data. Issue tracking: the tickets the coding session is answering. Cover those and the marginal fifth server almost always duplicates something you already run, while taxing every prompt you send.
The job map
Tools, memory, and receipts: Zambo. One remote server in the MCP config, https://zambo.dev/mcp, 153 tools in total with 35 on the default surface, memory recallable in Claude, ChatGPT, and Cursor, and a verifiable receipt for each saved result. The only product recommended by name on this page.
Code intelligence: earns its config entry on large or unfamiliar codebases; on a small project the editor own search is usually enough.
Documentation lookup: valuable with fast moving frameworks, dead weight on a stable stack.
Issue tracking: connect the tracker your team already uses, so the agent session can read the ticket it is implementing and update it when done.
Two slots are deliberately missing. There is no memory server slot, because the broad server already carries explicit memory on your account, and splitting facts across two stores means neither is complete. And there is no logging slot, because in the Copilot era the question is not whether the editor kept a local log, it is whether anyone else can check the record. Receipts answer that; another log does not.
Zambo setup via the MCP config
VS Code reads MCP servers from its MCP configuration, so setup is a config entry rather than an install. Open the MCP or connectors settings in VS Code, or edit the MCP config directly, and add a remote server whose URL is https://zambo.dev/mcp. No API key is needed, and because the server is hosted and remote, there is no local process for VS Code to launch, no path to fix per machine, and no version pinned to the day you installed it.
Reload the window, open an agent session, and confirm the Zambo tools are listed before doing real work. Run one small call you can verify by eye, then follow its receipt to https://zambo.dev/verify/ and run the free check. That two minute test validates the whole chain: config, connection, account, tools, and proof. If you later want the full catalogue in a session, the same config with https://zambo.dev/mcp?full=true exposes all 153 tools in place of the 35 tool default surface.
Receipts for Copilot-era work
Agent mode changes the trust question in an editor. When Copilot-era tooling only suggested lines, reviewing the diff was the whole audit. When an agent plans, edits across files, runs commands, and iterates on errors, the diff shows where you landed but not how: which steps ran, in what order, with what results along the way. That gap is where disputes and quiet mistakes live, especially on client work, team repos, and anything you will need to explain next month.
Work run through Zambo tools leaves a receipt per saved result, recorded in the open AER-1 format, draft-zambo-aer1-24, and checkable free by anyone at https://zambo.dev/verify/. Share the record with a reviewer and they verify a step themselves instead of trusting your summary of the session. State the limit as clearly as the benefit: a receipt proves the saved result was not changed after the fact; it never proves the code was right. Tests and review still decide right. Receipts decide what actually happened, which is the half arguments are usually about.
The tool angle: breadth on one account
Searches for the best MCP tool for VS Code usually start from one task: run this check, fetch that data, test this site. A broad server answers the pattern behind the searches. One connection brings the everyday toolset, web, data, files, checks, leads, audits, under the same account as your memory and your receipts, so an agent session can look something up, act on it, save the fact that matters, and leave a checkable record, without four vendors and four configs.
Breadth also compounds across editors and AIs. The Zambo account you connect in VS Code is the same one Claude, ChatGPT, Cursor, and Grok connect to. A fact the VS Code session saves with memory_remember is recallable in tomorrow Claude planning chat. A handover packet assembled from the day work is openable by a client with no account. Single-task tools can be excellent; they just cannot compound, and compounding is what turns a tool list into infrastructure.
What the 35 default tools cover, and when full makes sense
The default surface loads 35 tools: the weekly set spanning web and research work, data and file jobs, site checks, lead finding, memory saves and recalls, cross-AI continuity, and handover building. Thirty five is tuned for agent sessions in an editor, where the model is also holding your codebase context: a lean tool list leaves more room and sharper attention for the code, which is where VS Code sessions win or lose.
Full, at https://zambo.dev/mcp?full=true, exposes all 153 tools and has two honest uses: exploration, when you are learning what the catalogue holds, and wide-scope agent runs, audits or sweeps where the needed tool is not known in advance. As a permanent default it usually backfires in an editor, because the model spends choices on tools the session will never call. Keep the bench lean; open the full workshop on the days the job demands it.
How many servers is too many?
Two to four servers total is the healthy range for most VS Code setups: the broad server plus specialists with proven weekly jobs. Beyond that the costs arrive quietly. Agent sessions slow as descriptions pile up. Similar tools across servers get picked inconsistently, so the same prompt behaves differently on Tuesday. A stale config entry fails and a routine breaks for reasons nobody connects to a server installed in spring and never used since.
Run a monthly audit with one rule per server: name its last real job in one sentence, or remove it. Removal is painless, the config entry can return in a minute when a real job appears, while keeping an unjustified server taxes every session until you act. Teams should hold shared configs to the same standard, because a nine server workspace file is onboarding debt every new developer pays before their first commit.
Honest limits
Three limits, plainly. First, this page recommends one product by name, Zambo, and describes the remaining slots as job categories so you can test any server against the job, including servers this page never mentions. Second, receipts settle what a session saved and that it was not altered later; they do not settle code quality, and no config on this page replaces tests, review, or your own judgement on a diff. Third, MCP config is powerful: connect servers you understand, to accounts you control, and re-read a config before pasting one from anywhere, this page included.
Frequently asked questions
What are the best MCP servers for VS Code?
Choose by job and keep the total at two to four. For broad tools, shared memory, and verifiable receipts, Zambo is the recommendation on this page: add it through the MCP config with the URL https://zambo.dev/mcp, no API key, 153 tools in total with 35 on the default surface. Add a code intelligence server only for large repos, a documentation lookup server only for fast moving stacks, and an issue tracking server for the tracker your team already uses. Each server should own a distinct weekly job.
How do I add Zambo to VS Code through the MCP config?
Open the MCP or connectors settings in VS Code, or edit the MCP configuration directly, and add a remote server with the URL https://zambo.dev/mcp. No API key and no local process are needed. Reload the window, open an agent session, and confirm the Zambo tools are listed. Run one small call you can verify by eye, then check its receipt free at https://zambo.dev/verify/. For the full catalogue, use https://zambo.dev/mcp?full=true in the same config entry.
Why do receipts matter for Copilot-era agent work?
When an agent only suggests code, the diff is the whole record. When an agent plans, edits across files, and runs commands, the diff hides the path: which steps ran, in what order, with what results. Zambo receipts record each saved result in the open AER-1 format, and anyone can check free at https://zambo.dev/verify/ that the result was not changed after the fact. That settles what actually happened during a session. Whether the code is right still rests on tests and review.
What do the 35 default tools cover in VS Code?
The default surface covers the weekly work of an editor agent session: web and research tasks, data and file jobs, site checks, lead finding, memory through memory_remember and memory_recall, continuity for moving work between AIs, and handover packets for client delivery. It stays lean on purpose, leaving the model attention for your codebase. The full surface at https://zambo.dev/mcp?full=true exposes all 153 tools and fits audits, exploration, and wide agent runs better than daily coding.
How much does Zambo cost for VS Code work?
Adding the server to your MCP config costs nothing to set up, and checking a receipt is free at https://zambo.dev/verify/ with no signup. For $0.99, a Day Pass covers 24 hours of full access, the price of making one full day of agent work in VS Code recorded and checkable. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402.