Skip to content
Vinkius

DeepSource Connector for AI agents.

14 live capabilities

Monitor code quality and security vulnerabilities across your entire codebase.

Live agent request DeepSource / Connector

Waiting for input…

AI Agent

Why people use DeepSource

DeepSource Code Quality Analysis for Engineering Teams

This Connector changes that by putting the data where you already work. You can ask your agent to summarize the report card or find specific bugs in a file. You get a clear picture of your technical debt without ever leaving your IDE.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

That it puts your entire code quality dashboard into a simple chat interface.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Security Audit

    A security lead asks the agent to find all critical CVEs in the 'frontend' repo.

  2. Real-world use case 02

    PR Review

    A developer wants to know if their new code increased complexity.

  3. Real-world use case 03

    Manager Overview

    An engineering manager asks for a summary of all repository grades.

Complete set · 14capabilities

The complete DeepSource capability set.

These are the exact actions your AI can choose when you ask it to work with DeepSource.

Capability set01 / 04

01—04

4 capabilities in this set.

Part of 14 available through DeepSource.

  1. 01 Capability

    Activate repository

    Turns on code quality monitoring for a repository so it starts receiving analyses. Use this to enable monitoring for a project that was previously inactive.

  2. 02 Capability

    Deactivate repository

    Pauses analysis for a repository to stop billing or archive the project. This stops new analyses from running until you reactivate it.

  3. 03 Capability

    Get report card

    Fetches the high-level health grade and score breakdown for a repository. It provides a quick check of your overall code quality status.

  4. 04 Capability

    Get repository metrics

    Returns specific data points like line coverage or cyclomatic complexity for a repo. You can filter by specific metric shortcodes if needed.

Capability set02 / 04

05—08

4 capabilities in this set.

Part of 14 available through DeepSource.

  1. 05 Capability

    Get repository

    Retrieves the configuration details for a repository to help identify its unique ID. Use this to inspect a repo before querying issues or metrics.

  2. 06 Capability

    Get test coverage

    Shows the current percentage of code covered by tests against your set thresholds. This helps ensure your code meets your team's testing standards.

  3. 07 Capability

    Get viewer

    Verifies your API token is active and pulls your account profile details. Use this to confirm your connection to DeepSource is working correctly.

  4. 08 Capability

    Get vulnerability

    Provides deep-dive details on a specific dependency vulnerability using its unique ID. This helps you understand a risk before deciding on a fix.

Capability set03 / 04

09—11

3 capabilities in this set.

Part of 14 available through DeepSource.

  1. 09 Capability

    List analysis runs

    Shows the history of recent analysis runs including status and the specific analyzer used. You can filter these results by branch name.

  2. 10 Capability

    List issues

    Lists code quality problems like smells and bugs along with their file paths and lines. This helps you identify anti-patterns across your codebase.

  3. 11 Capability

    List sca targets

    Shows which dependency manifest files like package.json or requirements.txt are being scanned. This clarifies which files are being monitored for security.

Capability set04 / 04

12—14

3 capabilities in this set.

Part of 14 available through DeepSource.

  1. 12 Capability

    List vulnerabilities

    Lists all security risks in your dependencies including CVE IDs and fixability status. Use this to prioritize which security flaws to tackle first.

  2. 13 Capability

    Regenerate dsn

    Invalidates the current Data Source Name and generates a new one for a repository. This is the best way to rotate your credentials if they get compromised.

  3. 14 Capability

    Update default branch

    Changes the branch DeepSource analyzes as the default for a specific repository. This is useful when your team migrates from master to main.

Set up in minutes

One URL. Then ask DeepSource to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use DeepSource from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_gRojrYBqBJYk2MB0kmqFd1Bq7M9JWeWmipQYTeBA/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it DeepSource, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable DeepSource for the conversation.

Where the request belongs

Work DeepSource can move forward.

Built around the request

For engineers and security leads who are tired of manual audit cycles and want to see the truth about their code health instantly.

01

Engineering Manager

Reviews code quality grades and issue counts across 20 repositories in a single chat session.

02

Security Analyst

Monitors dependency vulnerabilities and prioritizes remediation based on reachability status.

03

Software Engineer

Checks cyclomatic complexity and test coverage before merging a feature branch.

04

DevOps Lead

Manages repository activation and DSN rotation at scale across the organization.

Build the capability set

Add more capabilities.

Each Connector adds new actions and data without changing how you work.

Browse Connectors
Codacy logo
01 8 capabilities

Codacy

Manage code quality and automated reviews via Codacy. track grades, monitor issues, and audit repository analysis directly from any AI agent.

View Connector
SonarCloud logo
02 9 capabilities

SonarCloud

Merge your SaaS DevOps workflow with SonarCloud to review AI code and prevent production vulnerabilities.

View Connector
SonarQube & SonarCloud logo
03 10 capabilities

SonarQube & SonarCloud

Bring your standalone or cloud SonarQube quality gates native to your AI logic. Find bugs, duplications, and rewrite vulnerable code instantly.

View Connector
Codecov logo
04 8 capabilities

Codecov

Manage test coverage and engineering metrics via Codecov. track coverage reports, monitor commit totals, and audit code quality directly from any AI agent.

View Connector
Code Integrity Prover logo
05 1 capability

Code Integrity Prover

AI agents default to type evasion (like any, void*, unsafe, or ignore), TODO stubs, timing/sleep hacks, and empty catch blocks. 96% of developers don't trust AI-generated code. This capability enforces zero-workaround integrity across all programming languages.

View Connector
CodeRabbit logo
06 9 capabilities

CodeRabbit

Manage AI-powered code reviews via CodeRabbit. list users, track PR review metrics, audit admin actions, and control seat assignments from any AI agent.

View Connector

Bring your own AI

Change the model, client or framework. Keep DeepSource connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about DeepSource.

The practical details behind the request, access and result.

How does the DeepSource MCP help with security?

It connects your security scan data to your AI agent. You can ask it to list all active vulnerabilities, check for specific CVE IDs, and see which risks are actually reachable in your code so you can prioritize fixes.

Can I use DeepSource MCP to see my code's cyclomatic complexity?

Yes, the Connector can pull specific metrics like cyclomatic complexity and maintainability index. You can ask your agent to check these for any repository to identify complex functions that need refactoring.

Does DeepSource MCP work with my existing DeepSource account?

It does. You just need to provide your DeepSource Personal Access Token when connecting the Connector to your AI client. This allows your agent to access the data from your existing projects.

How do I see my repository's health grade?

You can simply ask your AI agent for the report card of any repository. It will pull the overall grade, the score breakdown, and a summary of the health trends for you.

Can the DeepSource MCP manage my repository settings?

Yes, it can handle several management tasks. You can ask your agent to activate or deactivate repositories, update default branches, or even rotate your DSN tokens without leaving your chat.

Will DeepSource MCP show me which files have the most code smells?

Yes, it can list all code quality issues and include the specific file paths and line numbers for each. This makes it easy to see exactly where the most problematic code lives.

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/.

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.

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.

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.

One connection away

Give your agent a direct line to DeepSource.

Connect DeepSource once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available