MCP servers for VS Code
VS Code reads MCP servers from a workspace or user mcp.json, so a server can be scoped to one repository or to every project you open.
Connect BusinessMCP to VS Code
One entry for every tool you have connected, rather than one config block per server with its own credential. Add this to .vscode/mcp.json:
- 1Create .vscode/mcp.json in your repository, or use the user-level config to make the server available in every project.
- 2Paste the block above with a key from your BusinessMCP dashboard.
- 3Reload the window. The server appears in the chat view tool picker.
- 4Ask an agent-mode question that needs real data and it calls the tool instead of inferring an answer.
Servers worth connecting to VS Code
Official and verified entries from the directory. Each links to a detail page with its real tool list, example prompts and setup steps.
Stripe
Stripe, Inc.
Payments, subscriptions, invoices, and revenue analytics as agent-callable tools.
GitHub
GitHub
Repos, PRs, issues, and Actions — controllable from any agent thread.
Salesforce
Salesforce
Leads, opportunities, and pipeline state for outreach and sales agents.
Google Search Console
Query data, index coverage, and sitemap tools for SEO agent threads.
Meta Ads
Meta
Campaign creation, budgets, and creative deployment via the Meta Ads API.
Google Analytics
User counts, funnels, and traffic sources for your dashboard widgets.
Slack
Slack
Post updates, read channels, and bridge agent threads into your workspace.
free directory submitter
BusinessMCP
Automatically drafts and registers your startup to launch directories.
seo onpage auditor
BusinessMCP
Scrapes any URL and returns structured, prioritized SEO recommendations.
Frequently asked questions
Workspace config or user config?
Workspace config travels with the repository, so a teammate who clones it gets the same servers — which is what you want for anything project-specific. User config is right for your personal staples. Do not commit a credential either way: reference an environment variable or an input.
Does this work in Copilot agent mode?
Yes. MCP servers configured this way show up as tools in agent mode, alongside the built-in ones.
Can I point it at a local server instead?
Yes — a stdio entry runs a local command rather than calling a URL. A hosted endpoint is simpler when several people need the same tools, since nobody has to install anything.
One endpoint, every tool, in VS Code
Connect your stack once and it is reachable from VS Code — and from every other AI you use — without a config block per server.
Get started freeFree plan available · No credit card