Integrate DeepSource with Claude, Cursor, Chatbots & AI Agents MCP Server

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

Automate code quality monitoring via DeepSource — analyze issues, vulnerabilities, metrics, and report cards directly from any AI agent.

GDPR Free for Subscribers

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

activate

Activate repository on DeepSource

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

deactivate

Deactivate repository on DeepSource

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

get

Get report card on DeepSource

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

get

Get repository on DeepSource

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

get

Get repository metrics on DeepSource

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

get

Get test coverage on DeepSource

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

get

Get viewer on DeepSource

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

get

Get vulnerability on DeepSource

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

list

List analysis runs on DeepSource

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

list

List issues on DeepSource

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

list

List sca targets on DeepSource

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

list

List vulnerabilities on DeepSource

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)

regenerate

Regenerate dsn on DeepSource

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

update

Update default branch on DeepSource

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

Security & Code Integrity Audit

Every tool in the DeepSource MCP Server is continuously audited by the Vinkius Security Engine. We guarantee zero-trust payload isolation, strict data boundaries, and deterministic execution for enterprise-grade AI agents.

A+Score: 98.33

How Vinkius protects your data

Is there a risk of the AI "going crazy" and deleting important company data?

No. With Vinkius, the AI operates on "rails". It can only make the exact moves you authorized in the tool's settings. It cannot invent routes, access other networks in your company, or decide to delete random files. If the action isn't in the approved catalog, the attempt is blocked instantly.

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

How does the AI access my passwords and credentials?

It simply doesn't. On Vinkius, your passwords, API keys, and login details are kept in a secure vault. The AI (like ChatGPT or Claude) merely "asks" Vinkius to perform the task. Vinkius opens the door, does the work, and hands the result back to the AI. Your credentials are never seen, read, or learned by the artificial intelligence.

What if the AI ends up reading customer data or confidential information?

We have a built-in digital "bodyguard" called DLP (Data Loss Prevention). If a tool fetches data and the response contains social security numbers, credit cards, or personal customer info, Vinkius magically blocks and erases that information before it is delivered to the AI. The AI works only with what is strictly necessary, and your sensitive data never leaks.

DeepSource Capabilities for AI Assistants

Connect your AI agents and chatbots (Claude, ChatGPT, Cursor) with the DeepSource MCP server to manage operations across the following domains.

Intelligent code review Management

The DeepSource integration allows Cursor and ChatGPT to securely fetch code review data. It handles the API requests required for developer tools operations.

Autonomous static analysis Strategies

The DeepSource server exposes documented endpoints for static analysis. This allows ChatGPT and Cursor to interact with developer tools APIs seamlessly.