Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use DeepSource with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Automate code quality monitoring via DeepSource. analyze issues, vulnerabilities, metrics, and report cards directly from any AI agent.

Included with plan

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

Complete set · 14 capabilities

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

    Activate repository

    Once activated, DeepSource will start analyzing the code on each push/PR. You must provide the repository ID (obtained from get_repository). Use this to enable code quality monitoring for a repository that was previously inactive. Activate a repository for code analysis in DeepSource

  2. 02

    Get report card

    This provides a quick health check of the repository's overall code quality status. You must provide the repository name, login, and VCS provider. Use this to get a high-level view of code quality trends and identify areas needing improvement. Get the overall report card (grade) for a repository

  3. 03

    Get repository

    You must provide the repository name, login (user or org name), and VCS provider (e.g., GITHUB, GITLAB, BITBUCKET). Use this to inspect repository configuration before querying issues, analyses, or metrics. Get details of a specific repository in DeepSource

  4. 04

    Get repository metrics

    You must provide the repository name, login, and VCS provider. Optionally filter by specific metric shortcodes (e.g., "LCV" for line coverage, "MI" for maintainability index, "CC" for cyclomatic complexity). If no shortcodes specified, returns all available metrics with their values and thresholds. Get code quality metrics for a repository

Capability set02 / 04

05-08

4 capabilities in this set.

Part of 14 available through DeepSource.

  1. 05

    List analysis runs

    You must provide the repository name, login, and VCS provider. Optionally filter by branch name and limit the number of results (default: 20). Each run shows which analyzer was used (e.g., PYTHON, JAVASCRIPT, GO) and whether the analysis succeeded or failed. List recent code analysis runs for a repository

  2. 06

    List issues

    You must provide the repository name, login, and VCS provider. Optionally filter by analyzer short code (e.g., "PYTHON", "JS-A1") and limit results (default: 50). Each issue includes up to 3 sample occurrences with file path and line number. Use this to identify code smells, anti-patterns, and potential bugs across your codebase. List code quality issues in a repository

  3. 07

    List sca targets

    Each target includes ecosystem (e.g., npm, pip, gem), package manager, manifest file path, and activation status. You must provide the repository name, login, and VCS provider. Use this to understand which dependency files are being scanned for vulnerabilities. List all SCA (Supply Chain Analysis) targets in a repository

  4. 08

    List vulnerabilities

    Each vulnerability includes severity, CVE ID, CVSS score, description, affected package name and version, reachability status, and fixability. You must provide the repository name, login, and VCS provider. Optionally limit the number of results (default: 20). Use this to identify security risks in your dependencies and prioritize remediation. List dependency vulnerabilities in a repository (SCA)

Capability set03 / 04

09-11

3 capabilities in this set.

Part of 14 available through DeepSource.

  1. 09

    Update default branch

    This affects which branch is analyzed by default. You must provide the repository ID (from get_repository) and the new branch name (e.g., "main", "develop", "master"). Use this when your team changes the default branch name (e.g., migrating from "master" to "main"). Update the default branch for a repository in DeepSource

  2. 10

    Deactivate repository

    No new analyses will run until the repository is reactivated. You must provide the repository ID (obtained from get_repository). Use this to pause analysis for archived repositories or when you want to stop billing for a specific repository. Deactivate a repository to stop code analysis in DeepSource

  3. 11

    Get test coverage

    Shows the coverage percentage value and any configured thresholds. You must provide the repository name, login, and VCS provider. Use this to monitor code quality and ensure adequate test coverage across your codebase. Get test coverage metrics for a repository

Capability set04 / 04

12-14

3 capabilities in this set.

Part of 14 available through DeepSource.

  1. 12

    Get viewer

    Use this to verify your API token is working and to get your user details from DeepSource. Get the authenticated user profile from DeepSource

  2. 13

    Get vulnerability

    You must provide the repository name, login, VCS provider, and the vulnerability occurrence ID (obtained from list_vulnerabilities). Use this to deep-dive into a specific vulnerability before deciding on remediation steps. Get details of a specific dependency vulnerability by its ID

  3. 14

    Regenerate dsn

    The DSN is used to authenticate DeepSource analysis runs. You must provide the repository ID (obtained from get_repository). This action invalidates the old DSN and returns the new one. Use this if you suspect the DSN has been compromised or needs rotation. Regenerate the DSN (Data Source Name) for a repository

Observed, not estimated

925ms average. Fast in production.

DeepSource is checked daily against the live service.

Daily averagePeak 1111ms
Aug 20Today
Fastest day
790ms
Slowest day
1111ms
14-day trend
Slowing+10%

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

FAQ

Questions DeepSource owners ask.

  • 01

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

  • 02

    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.

  • 03

    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.

  • 04

    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.

Explore

More in Developer Tools

Suggestions