How to Use the DeepSource MCP in VS Code Copilot

Q: How do we check recent build runs in VS Code Copilot?

Ask the agent to list recent runs using the listanalysisruns tool. It will return the status and analyzer type for your latest commits.

Q: Does this tool support multiple repository providers?

Yes. When calling getrepository, you specify GITHUB, GITLAB, or BITBUCKET as the VCS provider, allowing Copilot to fetch the correct settings.

Share DeepSource quality metrics and security alerts with your entire development team inside VS Code Copilot with this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect DeepSource MCP to VS Code Copilot

Create your Vinkius account to connect DeepSource to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup DeepSource with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share code quality checks across your team

Commit your configuration to Git using `.vscode/mcp.json` to give your entire team access to static analysis tools. Copilot can run `get_report_card` to verify the overall health of your repository during code reviews. This setup ensures everyone on your engineering team uses the same quality standards. Developers don't need to configure individual API endpoints to query `get_repository_metrics`.

Audit supply chain vulnerabilities in VS Code Copilot

Manage security risks during your team's development cycle. Copilot calls `list_vulnerabilities` to check for CVEs and CVSS scores in your active dependencies. When a vulnerable package is found, the agent uses `get_vulnerability` to inspect the affected versions. Your team can quickly apply patches before code reaches your staging environment.

Manage repository analysis settings via MCP Server

Keep your static analysis configuration in sync with your development workflow. The MCP Server allows Copilot to run `update_default_branch` when you switch your main development target. If you need to stop analysis for archived repositories, the agent can trigger `deactivate_repository`. This gives your team direct control over billing and active monitoring from the chat sidebar.

Setup guide

Set up DeepSource MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the DeepSource MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the DeepSource tools listed. Try asking: "List my recent DeepSource transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "deepsource-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DeepSource. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect DeepSource now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about DeepSource MCP in VS Code Copilot

Create a .vscode/mcp.json file in your repository root and check it into your version control. Every team member with VS Code 1.96 or higher will instantly gain access to the tools via the local MCP Server daemon.

Yes. You can ask Copilot to trigger an active check by calling `activate_repository` to start monitoring code quality on every push.

Ask the agent to list recent runs using the `list_analysis_runs` tool. It will return the status and analyzer type for your latest commits.

Yes. When calling `get_repository`, you specify GITHUB, GITLAB, or BITBUCKET as the VCS provider, allowing Copilot to fetch the correct settings.

All repository configuration data is transmitted over encrypted channels directly to your VS Code client. Vinkius runs the server in an ephemeral sandbox that immediately destroys all session data upon completion.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript