DeepSourceをChatGPT、Claude、Geminiに接続

• 01 / 02脆弱性監査の方法を確認する
• 02 / 02コード品質の監視方法

最速日

847ms

最遅日

1292ms

14日間の傾向

安定0%

DeepSource Connector

準備完了です。MCPクライアントを選択し、セットアップ手順に従ってください。

コネクタリンクhttps://edge.vinkius.com/vk_preview_gRojrYBqBJYk2MB0kmqFd1Bq7M9JWeWmipQYTeBA/mcpコピー

Claude Desktop

以下の手順で数秒で接続できます。

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.

設定 · claude_desktop_config.jsonコピー

{
  "mcpServers": {
    "deepsource-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_gRojrYBqBJYk2MB0kmqFd1Bq7M9JWeWmipQYTeBA/mcp"
    }
  }
}

• Claude
• ChatGPT
• Cursor
• VS Code
• Windsurf
• Claude Code
• JetBrains
• Cline

各クライアントの手順ガイドはこちらです。 接続方法

Claude向けのガイド付きセットアップ？ DeepSourceをClaudeや他のAIに設定する

このConnectorが対応するすべてのAIクライアントを見る ↑

• 01

  エンジニアリングマネージャー

  ダッシュボードを開くことなく、複数のリポジトリにわたるコード品質のグレードや問題数、分析ステータスを即座に把握できます。

• 02

  セキュリティチーム

  CVEの詳細やCVSSスコアを用いて依存関係の脆弱性を監視し、到達性に基づいて修正の優先順位を決定できます。

• 03

  開発者

  IDEから直接コードの問題やメトリクス、レポートカードを確認し、マージ前に品質問題を修正できます。

• 04

  DevOpsリード

  組織全体のリポジトリの有効化状態、デフォルトブランチ、DSNのローテーションなどを管理できます。

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

• 

  Katalon TestOps (AI Test Management) AIコネクタ

  Manage test orchestration via Katalon TestOps — rerun test runs, monitor execution results, and audit software

  表示
• 

  Codacy AIコネクタ

  Manage code quality and automated reviews via Codacy — track grades, monitor issues, and audit repository anal

  表示
• 

  Beagle Security AIコネクタ

  Automate security testing via Beagle Security — list projects, start tests, and retrieve results directly from

  表示
• 

  Mabl (AI-Powered Test Automation) AIコネクタ

  Manage E2E testing via Mabl — trigger test plans, monitor execution results, and perform AI-driven failure ana

  表示

おすすめ

• 

  Codecov AIコネクタ

  Manage test coverage and engineering metrics via Codecov — track coverage reports, monitor commit totals, and

  表示
• 

  CodeRabbit AIコネクタ

  Manage AI-powered code reviews via CodeRabbit — list users, track PR review metrics, audit admin actions, and

  表示
• 

  Testim AIコネクタ

  Trigger automated AI tests, inspect execution logs, and manage branches natively via your AI agent.

  表示
• 

  Security Vulnerability Scanner AIコネクタ

  Scans code for security vulnerabilities like SQL injection and command injection using AST pattern matching.

  表示