An astronaut overseeing a futuristic data hub

Connect DeepSource to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Monitor vulnerabilities and code health without leaving your IDE.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 14 capabilities

We ship only the actions that matter.

Capability set01 / 04

01-04

4 capabilities in this set.

Part of 14 available through DeepSource.

  1. 01

    Activate repository

    Enable DeepSource to start analyzing code on every push or pull request. You just need to provide the repository ID to turn on monitoring for an inactive repo.

  2. 02

    Get report card

    Retrieve a high-level health grade for a repository. This capability provides an overall score and trend analysis to show how code quality is changing.

  3. 03

    Get repository

    Fetch configuration details for a specific repository. Use this to check settings before running deeper queries on issues or metrics.

  4. 04

    Get repository metrics

    Pull specific code quality data like maintainability index, cyclomatic complexity, or line coverage. You can filter for specific metrics using shortcodes.

Capability set02 / 04

05-08

4 capabilities in this set.

Part of 14 available through DeepSource.

  1. 05

    List analysis runs

    View the history of recent analysis executions. It shows the status, the branch used, and which analyzer was applied to the code.

  2. 06

    List issues

    Get a list of code smells, anti-patterns, and bugs. It provides file paths and line numbers for the detected issues.

  3. 07

    List sca targets

    Identify which dependency manifest files are currently being scanned for supply chain security. This shows the ecosystem and package manager for each target.

  4. 08

    List vulnerabilities

    List dependency vulnerabilities found in your project. It includes CVE IDs, CVSS scores, and whether the vulnerability is actually reachable in your code.

Capability set03 / 04

09-11

3 capabilities in this set.

Part of 14 available through DeepSource.

  1. 09

    Update default branch

    Change which branch DeepSource analyzes by default. This is useful when you migrate from master to main or change your primary development branch.

  2. 10

    Deactivate repository

    Stop code analysis for a specific repository. Use this to pause monitoring for archived projects or to manage your billing.

  3. 11

    Get test coverage

    Check your current test coverage percentages. It also returns any configured thresholds to see if you are meeting your team's requirements.

Capability set04 / 04

12-14

3 capabilities in this set.

Part of 14 available through DeepSource.

  1. 12

    Get viewer

    Verify your connection by retrieving your authenticated DeepSource user profile.

  2. 13

    Get vulnerability

    Get deep-dive details on a specific dependency vulnerability. You use the occurrence ID to see the full context of a security risk.

  3. 14

    Regenerate dsn

    Create a new DSN token for a repository. This invalidates the old token, which is necessary if you suspect a security compromise.

Real work

What teams actually run

01

Pre-merge Quality Checks

A developer asks the agent for the latest test coverage and issues to ensure a PR meets standards.

02

Security Incident Response

A security lead queries for critical vulnerabilities in specific packages to assess immediate risk.

03

Engineering Oversight

A manager requests a summary of report cards for all active repositories to track technical debt.

04

Automated Maintenance

A DevOps engineer uses the agent to update default branches or rotate DSN tokens after a security event.

Automate a task

Put DeepSource to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

DeepSource works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put DeepSource to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

998ms average. Fast in production.

DeepSource is checked daily against the live service.

Daily averagePeak 1292ms
Oct 3Today
Fastest day
847ms
Slowest day
1292ms
14-day trend
Stable0%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 14 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of DeepSource, so you can see the experience inside your AI.

It does not authenticate your account with DeepSource. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

DeepSource Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_gRojrYBqBJYk2MB0kmqFd1Bq7M9JWeWmipQYTeBA/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — DeepSource capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "deepsource-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_gRojrYBqBJYk2MB0kmqFd1Bq7M9JWeWmipQYTeBA/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up DeepSource in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work DeepSource owners hand off.

This MCP is built for technical teams that need to keep a pulse on code health without constantly switching tabs.

  • 01

    Engineering Managers

    They ask the agent for high-level health grades and issue counts across multiple repos.

  • 02

    Security Teams

    They use the agent to monitor CVEs and prioritize fixes based on CVSS scores and reachability.

  • 03

    Developers

    They check specific code issues and test coverage directly from their IDE.

  • 04

    DevOps Leads

    They manage repository activation and DSN rotation through the agent.

FAQ

Questions DeepSource owners ask.

  • 01

    How do I connect DeepSource to my AI client?

    Subscribe to the MCP on Vinkius and enter your DeepSource Personal Access Token. Once connected, you can use it immediately in any compatible client like Claude or Cursor.

  • 02

    Can I manage my repositories through the AI?

    Yes. You can use the MCP to activate or deactivate repositories, update default branches, and regenerate DSN tokens.

  • 03

    What kind of security data can my agent access?

    Your agent can list dependency vulnerabilities, check CVE IDs, view CVSS scores, and determine if a vulnerability is reachable in your code.

  • 04

    Does this work with GitHub and GitLab?

    Yes. The MCP works with repositories hosted on GitHub, GitLab, and Bitbucket.

  • 05

    Can I check test coverage with this MCP?

    Yes. You can ask your agent to retrieve test coverage percentages and compare them against your configured thresholds.

  • 06

    How do I get a DeepSource Personal Access Token and where do I find it?

    Log in to your DeepSource account, go to Account Settings → Personal Access Tokens, and click Create New Token. Give it a descriptive name (e.g., 'Vinkius MCP') and copy the token immediately. it won't be shown again. Paste this token into the API key field below. The token is used as a Bearer token in the Authorization header for all GraphQL requests to https://api.deepsource.com/graphql/.

  • 07

    What types of code issues can DeepSource detect and how are they categorized?

    DeepSource detects various code quality issues including code smells, anti-patterns, performance issues, security vulnerabilities, and bugs. Issues are categorized by severity (CRITICAL, HIGH, MEDIUM, LOW) and by analyzer type (e.g., PYTHON for Python issues, JS-A1 for JavaScript anti-patterns, GO for Go issues). Each issue includes a shortcode, title, category, and file locations with line numbers. You can filter issues by analyzer short code when querying repositories.

  • 08

    How does DeepSource detect dependency vulnerabilities and what information is provided?

    DeepSource uses Supply Chain Analysis (SCA) to scan dependency manifest files (package.json, requirements.txt, Gemfile, etc.) for known vulnerabilities. Each vulnerability includes: CVE ID, CVSS score (0-10), severity level, description, affected package name and version, ecosystem (npm, pip, etc.), reachability status (whether the vulnerable code is actually called), and fixability (whether a fix version is available). This helps prioritize which vulnerabilities to address first based on real risk rather than just theoretical severity.

  • 09

    What is the API rate limit and how many requests can I make per hour?

    DeepSource enforces a rate limit of 5,000 requests per hour per user account. This limit covers both read (queries) and write (mutations) operations. If you exceed this limit, the API will return HTTP 429 (Too Many Requests). For most code review and monitoring workflows, this limit is more than sufficient. If you need higher limits for large-scale analysis, contact DeepSource support.

Connect DeepSource to Claude, Cursor, ChatGPT & more