Skip to main content The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery

VS Code MCP Server

Turn VS Code into an enterprise agent

Let your employees delegate real work to VS Code across all their apps, under their own identity and permissions.

DrataGPLocalyzeFlipMindtoolsScreenloop

Get VS Code to work.
Not just chat.

One connection to StackOne, and VS Code gets scoped access to every app your employees use, to act on their behalf.

Connect

Make every system AI-ready

Give your AI access to 450+ managed MCP servers and 28,000+ tested tools. No auth code to write, no API maintenance.

Secure

Keep AI under control

Enforce identity-based access, screen every response for prompt injection, and audit every action.

Optimize

Trust what AI delivers

Keep your agent sharp with lean tool loading, boost reliability with the Falcon execution engine, and enhance its context with pre-synced data.

Roll out MCP tools to every VS Code user.
Set up and onboarding in minutes.

One-time setup for IT. Self-serve for everyone else.

IT Admin

One-time setup, no per-user wiring.

The URL carries no access on its own, so it is safe to commit with the repo or publish in an internal wiki. There is no app registration to create and no client secret to hand out. VS Code setup guide →

Which MCP server will you
connect VS Code to?

Connect to the StackOne MCP gateway once and give your employees' agents instant access to 450+ pre-built SaaS connectors and 28,000+ MCP tools.

Need another connector? Build one with the AI Connector Builder

What will your employees
delegate to VS Code?

From HR and recruiting to sales and support, VS Code completes work across any app you connect.

HR & People Ops

> List this month's Workday work anniversaries and draft a personalized celebration message for each.

UKG ReadyWorkday (Rest and Soap)FactorialHiBobOracle Fusion HCMHumaansSAP SuccessFactorsClockify
Recruiting

> Compare Greenhouse interview feedback across stages and flag candidates trending toward an offer.

JobAdderVincereSmartRecruitersAshbyManatalFactorialHiBobSAP SuccessFactors
Sales & CRM

> Analyze Salesforce deals stuck 30+ days and draft a re-engagement email for each owner.

SalesforceKeapZoho CRMPipedriveFreshsalesJustCallPardotAircall
Support

> Cluster yesterday's Zendesk tickets by theme and surface the top 3 trending issues.

IntercomSurveyMonkeyFreshserviceServiceNowFreshdeskGorgiasDiscourseDixa

Not everyone on VS Code?
Your integration layer stays the same.

The same setup works across Coding agents like Cursor, Claude Code, and every other MCP client.

Explore MCP clients

Frequently Asked Questions

You connect VS Code to StackOne over MCP with one entry in .mcp.json: a servers key holding "stackone" with "type": "http" and "url": "https://mcp.stackone.com/mcp". Or run MCP: Add Server from the Command Palette. VS Code opens StackOne in your browser: sign in, pick your project and accounts, and authorize. Setup guide.
VS Code stores the StackOne MCP server config in .mcp.json in the workspace, under a servers key — not mcpServers, which other clients use — with each entry carrying its own type (http for StackOne). It's a plain file, so a team can commit it with the repo; it holds only the gateway address, never credentials.
Yes. MCP support in VS Code runs entirely through GitHub Copilot: you need the Copilot extension with Copilot Chat's Agent mode on, since that's the only mode where the agent can call tools — there's no MCP path that bypasses it. Once enabled, VS Code reads servers from .mcp.json. See the setup guide; the same gateway also works in Cursor.
You don't configure each app in StackOne yourself. IT connects the apps and sets the action ceiling for your project. VS Code sends you to a consent screen where you pick which of those accounts and actions to use, narrowing further if you want. Rerun the flow to change it.
Once connected, VS Code can run whatever actions you granted, across 450+ live connectors and 28,000+ tested actions — CRM, HRIS, ATS, ticketing, finance, and more. Tools go live as soon as you authorize, and the tools icon in Agent mode lists what came through. Browse the actions in the directory above.
Your app credentials — GitHub, Salesforce, and the rest — live server-side in StackOne and never reach VS Code or your machine. The gateway address in .mcp.json carries no access on its own, so it's safe to commit with the repo. There's no client ID or secret; VS Code registers itself during the OAuth handshake.
IT can roll out the StackOne MCP connector to a whole team in one pass: connect the apps once, and commit a single .mcp.json entry to the repo instead of briefing people individually. Each person still signs in, picks their own accounts and actions, and authorizes — so nobody exceeds the ceiling IT set.
Skip connecting VS Code to StackOne when any of these is true:
  • An existing first-party MCP server already covers your apps
  • You use only a handful of actions across a few apps
  • You don't need multi-tenancy or per-action scoping
  • Prompt injection isn't a concern
  • Nobody can complete a browser consent step — a CI job or headless server, for instance

Connect All Your Apps to VS Code.

One URL, 450+ pre-built SaaS connectors. Set up in minutes.