DeepSource MCP Server for Claude Desktop 14 tools — connect in under 2 minutes
Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install DeepSource and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"deepsource": {
// Your Vinkius token. get it at cloud.vinkius.com
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About DeepSource MCP Server
Connect your DeepSource account to any AI agent and take full control of code quality analysis, vulnerability detection, and metrics monitoring through natural conversation.
Claude Desktop is the definitive way to connect DeepSource to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 14 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
What you can do
- Code Issues — List and inspect code quality issues (code smells, anti-patterns, bugs) across repositories with severity and file locations
- Analysis History — View recent analysis runs with status, branch, and analyzer information (Python, JavaScript, Go, etc.)
- Security Vulnerabilities — Identify dependency vulnerabilities (SCA) with CVE IDs, CVSS scores, reachability, and fixability status
- Code Metrics — Query maintainability index, cyclomatic complexity, lines of code, and test coverage percentages
- Report Cards — Get overall repository health grades (A-F) with score breakdowns and trend analysis
- SCA Targets — List all dependency manifest files being scanned for supply chain security
- Repository Management — Activate/deactivate repos, update default branches, and regenerate DSN tokens
The DeepSource MCP Server exposes 14 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect DeepSource to Claude Desktop via MCP
Follow these steps to integrate the DeepSource MCP Server with Claude Desktop.
Open Claude Desktop Settings
Go to Settings → Developer → Edit Config to open claude_desktop_config.json
Add the MCP Server
Paste the configuration above into the mcpServers section
Restart Claude Desktop
Close and reopen Claude Desktop to load the new server
Start using DeepSource
Look for the 🔌 icon in the chat. your 14 tools are now available
Why Use Claude Desktop with the DeepSource MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with DeepSource through the Model Context Protocol.
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
DeepSource + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the DeepSource MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
DeepSource MCP Tools for Claude Desktop (14)
These 14 tools become available when you connect DeepSource to Claude Desktop via MCP:
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
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
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
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
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
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
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
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
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
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
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
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)
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
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
Example Prompts for DeepSource in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop agent to start working with DeepSource immediately.
"Show me the overall code quality report card and current issues for the 'api-service' repository in the 'acme-corp' GitHub organization."
"Check for any critical or high severity dependency vulnerabilities in the 'web-frontend' repo and tell me which packages are affected."
"What's the test coverage for our 'backend-api' repository and show me the most recent analysis runs?"
Troubleshooting DeepSource MCP Server with Claude Desktop
Common issues when connecting DeepSource to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
DeepSource + Claude Desktop FAQ
Common questions about integrating DeepSource MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.What happens if the MCP server is temporarily unavailable?
Can I connect multiple MCP servers simultaneously?
mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.Is there a limit on the number of tools per server?
Does Claude Desktop support Streamable HTTP transport?
Connect DeepSource with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect DeepSource to Claude Desktop
Get your token, paste the configuration, and start using 14 tools in under 2 minutes. No API key management needed.