Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 10
- 4 7
- 3 1
- 2 0
- 1 0
Trust in production
- Trust it - 89%
- With caveats - 11%
- Wouldn't - 0%
100% would recommend this server
How reviewers scored it
- Setup & docs 4.3
- Auth experience 3.9
- Reliability 4.3
- Maintainer responsiveness 4.3
Why it got an A
This is VS Code's MCP client, not a server: it connects to the servers you configure, and each of those carries its own risk and its own grade. Backed by Microsoft with a monthly release cadence and no open MCP-specific advisories. Local stdio servers you add run code on your machine with your permissions, and sign-in is whatever each remote server asks for, so harden server by server.
How to connect
Built in. Enable AI features, then add servers in .vscode/mcp.json or via the MCP: Add Server commandIs VS Code MCP safe?
Is VS Code MCP safe to use?
VS Code MCP grades A (strong public trust signals). Login is optional, so check that it is turned on in your setup.
Does VS Code MCP have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does VS Code MCP support authentication?
Optionally. It can run with a login, but it does not require one, so turn it on.
Alternatives in Developer Tools
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
- A Dynatrace Remote MCP ServerDynatrace's hosted MCP server, running inside your Dynatrace SaaS environment, to run and explain DQL, look into problems, vulnerabilities and Kubernetes events, and forecast time series.
- A GitHub MCP ServerOfficial GitHub server for repos, issues, pull requests, Actions, and code security, hosted or local.
- A GitLab MCP ServerGitLab's built-in MCP server for projects, merge requests, work items, code, and CI pipelines, on GitLab.com or your own instance.
Embed this badge
[](https://trustedmcp.io/servers/vscode-mcp)<a href="https://trustedmcp.io/servers/vscode-mcp"><img src="https://trustedmcp.io/badge/vscode-mcp.svg" alt="TrustedMCP grade A" height="80"></a>Community reviews
Better than the DIY script it replaced
Of the VS Code integrations I tried, this one is the most predictable. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Good choice if you need VS Code in your agent.
Used for Automating release notes
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Easy win for our agent setup
Our agents call this dozens of times a day. Auth is optional, which is convenient locally. I turned it on before sharing it with the team.
Used for Generating boilerplate from existing patterns
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Our team uses it every day
Hooked VS Code MCP into Claude Code and it worked on the first try. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Good choice if you need VS Code in your agent.
Used for Debugging sessions in Cursor
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
No complaints after a month
Simple to set up in Cursor, simple to reason about. I run it with auth enabled. Without it I would not let it near anything shared. Happy to run it in production.
Used for Code review summaries for pull requests
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Recommended it to two teams already
Set this up for our team after comparing a few options. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. It is in our production agent and I sleep fine.
Used for Internal developer assistant
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Quietly reliable
Our agents call this dozens of times a day. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere.
Used for Generating boilerplate from existing patterns
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Clean integration, sensible permissions
Started with it as an experiment, now it is a fixture. I run it with auth enabled. Without it I would not let it near anything shared. It is in our production agent and I sleep fine.
Used for Keeping project tickets in sync with code changes
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Set it up once, forgot about it
Been running this for about a month now. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Releases come often and the changelog is clear. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Worth the five minutes to set up
Clear tool names, sensible outputs, very few surprises. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Happy to run it in production.
Used for Letting a coding agent open and triage issues
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Does what it says, no drama
Replaced a homegrown script with VS Code MCP and have not looked back. Auth is optional, which is convenient locally. I turned it on before sharing it with the team.
Used for Looking up VS Code data without leaving the editor
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Solid and well behaved
Clear tool names, sensible outputs, very few surprises. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Would recommend without hesitation.
Used for Keeping project tickets in sync with code changes
- Setup & docs 3/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Earned a permanent spot in my config
Installed it on a Friday, it was part of my workflow by Monday. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent.
Used for Looking up VS Code data without leaving the editor
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Surprisingly polished
Tried it on a side project first, then rolled it out at work. I run it with auth enabled. Without it I would not let it near anything shared. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Easy recommendation.
Used for Scripting routine maintenance tasks
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Exactly what I needed from VS Code
Been running this for about a month now. Auth is optional, which is convenient locally. I turned it on before sharing it with the team.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Trustworthy enough for real work
I use this almost daily. I run it with auth enabled. Without it I would not let it near anything shared.
Used for CI failure investigation
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
The VS Code integration I wanted
Replaced a homegrown script with VS Code MCP and have not looked back. Updates land regularly, and nothing broke when I upgraded. I run it with auth enabled. Without it I would not let it near anything shared. Would recommend without hesitation.
Used for CI failure investigation
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Works, just lock it down
Good for experimenting, still deciding about production. I run it with auth enabled. Without it I would not let it near anything shared. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Recommended, with sensible guardrails.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Good defaults, good docs
Simple to set up in Cursor, simple to reason about. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Filed an issue and got a reply within two days. Easy recommendation.
Used for Code review summaries for pull requests
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.