MCP Debugger B0418685

MCP开发工具

提供方 dennisonbertram

开发工具 stdio · 本地进程 API Key 社区 / 第三方 Claude DesktopClaudeVS Code
查看接入方式

一个全面的模型上下文协议(MCP)服务器,为LLM应用程序提供调试、测试、代码分析和代码质量检查功能,支持多种编程语言和运行时环境。

一句话选型结论

按资料字段整理

MCP Debugger B0418685 属于开发工具类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude Desktop、Claude、VS Code,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 21 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量21暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

LLM调试TypeScript本地部署代码分析多语言支持Git集成测试框架

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
docker run -p 3000:3000 -e WORKSPACE_DIR=/app mcp-debugger

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Docker,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 21 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 21 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Debugger B0418685当前 21 stdio · 本地进程 本地部署 有 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方dennisonbertram上游标注的维护方 dennisonbertram
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Docker本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

18.2 KB
来自项目仓库与上游目录的原文,未做删改

MCP Debugger Server

A comprehensive Model Context Protocol (MCP) server that provides debugging, testing, linting, and code analysis capabilities to LLM applications. This server enables AI assistants to interact with codebases through a standardized protocol, supporting multiple programming languages and runtimes.

Features

Resources

  • Workspace Files: Read files and file slices from the workspace
  • Git Integration: Access to git status, diff, and repository information
  • Debug Sessions: Real-time debug session state and thread information
  • Stack Traces: Current call stack frames and local variables
  • Test Reports: Test execution results and failure analysis
  • Lint Reports: Code quality and style analysis results
  • Logs: Structured logging with filtering and search capabilities

Tools

  • Debug Session Management: Open/close debug sessions for multiple runtimes
  • Breakpoint Control: Set, clear, enable/disable breakpoints
  • Execution Control: Step into/over/out, continue, pause execution
  • Expression Evaluation: Evaluate expressions in debug contexts
  • Watch Expressions: Monitor variable values during execution
  • File Patching: Apply patches with safety confirmations
  • Testing: Run test suites and analyze results
  • Linting: Execute code quality checks
  • Command Execution: Run whitelisted system commands
  • Git Operations: Commit changes with human confirmation

Supported Runtimes

  • Node.js: Full Chrome DevTools Protocol (CDP) support
  • Python: Debug adapter protocol via debugpy
  • Go: Delve debugger integration
  • Java: JDWP (Java Debug Wire Protocol)
  • C#: .NET debugging via Visual Studio protocol
  • C/C++: GDB/LLDB integration
  • PHP: Xdebug support
  • Ruby: Ruby debugger integration
  • Rust: Native debugging support

Installation

Local Development Setup```bash

Clone the repository

git clone https://github.com/dennisonbertram/mcp-debugger.git
cd mcp-debugger

Install dependencies

npm install

Build the server

npm run build

Or run directly with ts-node (development)

npm run dev


### Cloud Code IDE Integration

#### Prerequisites
- Google Cloud Code extension installed in VS Code/IntelliJ
- Node.js 18+ installed
- Git repository initialized in your project

#### Quick Start with Cloud Code

1. **Install the MCP Debugger Server globally:**```bash
npm install -g https://github.com/dennisonbertram/mcp-debugger.git
  1. Add to your Cloud Code MCP configuration:```json
    {
    "mcp": {
    "servers": {
    "debugger": {
    "command": "mcp-debugger-server",
    "args": [],
    "env": {
    "WORKSPACE_DIR": "${workspaceFolder}"
    }
    }
    }
    }
    }

3. **Alternative: Run locally in your project:**```bash
# Add to package.json scripts
{
  "scripts": {
    "mcp-debugger": "node dist/index.js"
  }
}

Cloud Code Configuration File

Create or update your .vscode/settings.json:```json
{
"cloudcode.mcp.enabled": true,
"cloudcode.mcp.servers": {
"debugger": {
"command": "node",
"args": ["${workspaceFolder}/node_modules/@dennisonbertram/mcp-debugger/dist/index.js"],
"env": {
"WORKSPACE_DIR": "${workspaceFolder}",
"LOG_LEVEL": "info"
}
}
}
}


#### IntelliJ Cloud Code Configuration

For IntelliJ IDEA with Cloud Code:

1. Go to **Settings** → **Tools** → **Cloud Code** → **MCP**
2. Add new MCP server:
   - **Name**: MCP Debugger
   - **Command**: `node`
   - **Arguments**: `${project.dir}/node_modules/@dennisonbertram/mcp-debugger/dist/index.js`
   - **Environment Variables**:
     - `WORKSPACE_DIR=${project.dir}`
     - `LOG_LEVEL=info`

### MCP-Cloud Platform Deployment

For cloud-hosted deployment using MCP-Cloud platform:```bash
# Deploy to MCP-Cloud (requires API key)
curl -X POST https://api.mcp-cloud.ai/v1/servers \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-debugger-server",
    "template": "custom",
    "env": {
      "WORKSPACE_DIR": "/app",
      "LOG_LEVEL": "info"
    }
  }'

Docker Deployment```dockerfile

FROM node:18-alpine

WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production

COPY dist/ ./dist/
EXPOSE 3000

CMD ["node", "dist/index.js"]
``````bash

Build and run

docker build -t mcp-debugger .
docker run -p 3000:3000 -e WORKSPACE_DIR=/app mcp-debugger


### MCP-Cloud Integration

The MCP Debugger Server can be deployed and managed through the MCP-Cloud platform for enterprise-scale usage:

#### Authentication Setup```bash
# Set API key for MCP-Cloud
export MCP_API_KEY="mcp_sk_your_api_key_here"

Python Client Integration```python

import requests

def debug_with_mcp(prompt, session_id=None):
url = "https://your-server.mcp-cloud.ai/v1/chat/completions"
headers = {
"Content-Type": "application/json",
"Authorization": f"Bearer {os.environ['MCP_API_KEY']}"
}

data = {
    "model": "claude-3-5-sonnet",
    "messages": [{"role": "user", "content": prompt}],
    "context_id": session_id  # For maintaining debug context
}

response = requests.post(url, headers=headers, json=data)
return response.json()

#### JavaScript/Node.js Client```javascript
async function debugWithMCP(prompt, sessionId = null) {
  const response = await fetch('https://your-server.mcp-cloud.ai/v1/chat/completions', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Bearer ${process.env.MCP_API_KEY}`
    },
    body: JSON.stringify({
      model: 'claude-3-5-sonnet',
      messages: [{ role: 'user', content: prompt }],
      context_id: sessionId
    })
  });

  return response.json();
}

Real-time Streaming with SSE```javascript

// Enable streaming for real-time debug output
const eventSource = new EventSource(
'https://your-server.mcp-cloud.ai/api/servers/debug-session/events',
{
headers: {
'Authorization': Bearer ${process.env.MCP_API_KEY}
}
}
);

eventSource.addEventListener('debug:output', (event) => {
const data = JSON.parse(event.data);
console.log('Debug output:', data.message);
});

eventSource.addEventListener('breakpoint:hit', (event) => {
const data = JSON.parse(event.data);
console.log('Breakpoint hit at line:', data.line);
});


### Workflow Integration (n8n, Zapier, etc.)

#### n8n Integration Example```javascript
// In an n8n Function node
const axios = require('axios');

async function debugCode(codeSnippet) {
  const response = await axios.post(
    'https://your-server.mcp-cloud.ai/v1/chat/completions',
    {
      model: "claude-3-5-sonnet",
      messages: [
        {
          role: "system",
          content: "You are a debugging assistant. Analyze the following code for issues."
        },
        {
          role: "user",
          content: codeSnippet
        }
      ],
      stream: true  // Enable streaming for real-time responses
    },
    {
      headers: {
        'Authorization': `Bearer ${$credentials.mcpApi.apiKey}`,
        'Content-Type': 'application/json'
      }
    }
  );

  return response.data;
}

Configuration

Environment Variables```bash

Workspace directory (defaults to current directory)

WORKSPACE_DIR=/path/to/your/project

Enable/disable dangerous features

ALLOW_FILE_PATCHES=true
ALLOW_COMMAND_EXECUTION=false

Limits and timeouts

MAX_EXECUTION_TIME_MS=30000
MAX_OUTPUT_BYTES=1048576

Logging

LOG_LEVEL=info


### Security Features

- **Path Traversal Protection**: All file operations are sandboxed to the workspace
- **Command Whitelisting**: Only approved commands can be executed
- **Patch Confirmation**: File patches require explicit confirmation
- **Output Limiting**: Prevents excessive memory usage from large outputs
- **Timeout Protection**: All operations have configurable timeouts

## Usage

### Starting the Server```bash
# Production build
npm start

# Development with auto-reload
npm run dev

# With custom workspace
WORKSPACE_DIR=/my/project npm start

MCP Client Integration

Claude Desktop (One-Line Setup)

Quick setup command:```bash

Add to Claude Desktop config (one line)

echo '{"mcpServers":{"debugger":{"command":"node","args":["/path/to/mcp-debugger/dist/index.js"],"env":{"WORKSPACE_DIR":"'"$PWD"'"}}}}' >> ~/Library/Application\ Support/Claude/claude_desktop_config.json


**Or manually edit the config file:**```bash
# macOS/Linux
code ~/Library/Application\ Support/Claude/claude_desktop_config.json

# Windows
code %APPDATA%\Claude\claude_desktop_config.json

Add this configuration:```json
{
"mcpServers": {
"debugger": {
"command": "node",
"args": ["/path/to/mcp-debugger/dist/index.js"],
"env": {
"WORKSPACE_DIR": "/path/to/your/project"
}
}
}
}


### Programmatic Client Integration

The server communicates via stdio using the MCP protocol. Connect it to any MCP-compatible client:```typescript
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";

// Create MCP client
const client = new Client({
  name: "my-debug-client",
  version: "1.0.0"
});

// Connect to the debugger server
const transport = new StdioClientTransport({
  command: "node",
  args: ["dist/index.js"]
});

await client.connect(transport);
await client.initialize();

Available Client Libraries

Python MCP Client```python

import asyncio
from mcp import ClientSession, StdioServerParameters
from mcp.client.stdio import stdio_client

async def main():
# Connect to MCP Debugger Server
server_params = StdioServerParameters(
command="node",
args=["/path/to/mcp-debugger/dist/index.js"],
env={"WORKSPACE_DIR": "/your/project"}
)

async with stdio_client(server_params) as (read, write):
    async with ClientSession(read, write) as session:
        await session.initialize()

        # Use debugging tools
        result = await session.call_tool("open_debug_session", {
            "kind": "node",
            "entry": "app.js"
        })

        print("Debug session opened:", result)

asyncio.run(main())


#### Java MCP Client```java
import io.modelcontextprotocol.client.McpClient;
import io.modelcontextprotocol.client.transport.StdioClientTransport;

public class DebugClient {
    public static void main(String[] args) {
        // Create MCP client
        McpClient client = McpClient.builder()
            .name("Debug Client")
            .version("1.0.0")
            .build();

        // Connect via stdio
        StdioClientTransport transport = new StdioClientTransport(
            "node",
            List.of("/path/to/mcp-debugger/dist/index.js")
        );

        client.connect(transport);

        // Use debugging capabilities
        ToolResult result = client.callTool("open_debug_session",
            Map.of("kind", "node", "entry", "app.js"));

        System.out.println("Debug session: " + result);
    }
}

cURL for Testing```bash

Test server health

curl -X POST http://localhost:3000/health

Test MCP protocol (if using HTTP transport)

curl -X POST http://localhost:3000/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2025-06-18"},"id":1}'


### Example Workflow

1. **Open Debug Session**```typescript
const result = await client.callTool({
  name: "open_debug_session",
  arguments: {
    kind: "node",
    entry: "src/index.js",
    args: ["--port", "3000"]
  }
});
const sessionId = result.content[0].text.session_id;
  1. Set Breakpoints```typescript
    await client.callTool({
    name: "set_breakpoint",
    arguments: {
    session_id: sessionId,
    file: "src/server.js",
    line: 42,
    condition: "user.id > 0"
    }
    });

3. **Inspect State**```typescript
// Get stack trace
const stack = await client.callTool({
  name: "stack_trace",
  arguments: { session_id: sessionId }
});

// Evaluate expressions
const result = await client.callTool({
  name: "evaluate_expression",
  arguments: {
    session_id: sessionId,
    expression: "user.profile",
    frame_id: "frame_0"
  }
});
  1. Apply Fixes```typescript
    // Apply a patch (will require confirmation)
    await client.callTool({
    name: "apply_patch",
    arguments: {
    file: "src/buggy.js",
    start: 41,
    end: 43,
    replacement: "if (user && user.id > 0) {",
    require_confirmation: true
    }
    });

5. **Run Tests**```typescript
const testResult = await client.callTool({
  name: "run_tests",
  arguments: {
    runner: "npm",
    args: ["test", "--", "--grep", "user"]
  }
});

API Reference

Resources

workspace://file

Read files and file slices from the workspace.

Parameters:
- path: Relative path to file
- start: Starting line number (optional)
- end: Ending line number (optional)

Example:```
workspace://file?path=src/index.js&start=1&end=50


#### `debug://session/{sessionId}/state`
Get debug session state information.

#### `debug://session/{sessionId}/locals`
Get local variables for the current frame.

#### `logs://app`
Access application logs with filtering.

**Parameters:**
- `level`: Log level filter (debug, info, warn, error)
- `since`: ISO date string for start time
- `contains`: Text search in log messages
- `limit`: Maximum number of entries to return

### Tools

#### Debug Session Management
- `open_debug_session`: Start a new debug session
- `close_debug_session`: Terminate a debug session
- `list_debug_sessions`: List all active sessions

#### Breakpoint Control
- `set_breakpoint`: Set a breakpoint at a file location
- `clear_breakpoint`: Remove a breakpoint
- `list_breakpoints`: List all breakpoints in a session
- `toggle_breakpoint`: Enable/disable a breakpoint

#### Execution Control
- `continue_execution`: Continue from current breakpoint
- `step_into`: Step into function calls
- `step_over`: Step over function calls
- `step_out`: Step out of current function
- `pause_execution`: Pause running execution

#### Expression Evaluation
- `evaluate_expression`: Evaluate JavaScript/Python/etc. expressions
- `watch_expression`: Set up watch expressions
- `list_watch_expressions`: List active watch expressions
- `clear_watch_expression`: Remove watch expressions

#### Testing and Linting
- `run_tests`: Execute test suites
- `run_lint`: Execute code quality checks

#### File Operations
- `apply_patch`: Apply patches to files (with confirmation)
- `run_command`: Execute whitelisted system commands
- `git_commit`: Commit changes (with confirmation)

## Architecture

The server is built with a modular architecture:```
MCPDebuggerServer
├── Resources/
│   ├── WorkspaceResources    # File/Git operations
│   ├── DebugResources        # Debug session state
│   ├── TestResources         # Test/lint reports
│   └── LogResources          # Logging infrastructure
├── Tools/
│   ├── DebugSessionTools     # Session management
│   ├── BreakpointTools       # Breakpoint operations
│   ├── ExecutionTools        # Step/continue operations
│   ├── EvaluationTool        # Expression evaluation
│   ├── TestTools            # Testing operations
│   ├── LintTools            # Linting operations
│   ├── PatchTools           # File patching
│   ├── CommandTools         # Command execution
│   └── GitTools             # Git operations
└── Utils/
    ├── Logger               # Structured logging
    └── Config               # Configuration management

Each component is designed to be extensible and can be easily enhanced to support additional runtimes, tools, and resources.

Extending the Server

Adding New Runtimes

  1. Implement the DebuggerAdapter interface:```typescript
    class MyRuntimeAdapter implements DebuggerAdapter {
    // Implement required methods
    async launch(entry: string, args?: string[], env?: Record<string, string>): Promise<void> {
    // Start your runtime's debugger
    }

async setBreakpoint(bp: Breakpoint): Promise<Breakpoint> {
// Set breakpoint in your runtime
}

// ... other required methods
}


2. Register the adapter in `DebugSessionTools`:```typescript
if (args.kind === &#x27;myruntime&#x27;) {
  adapter = new MyRuntimeAdapter(cwd);
}

Adding New Tools

  1. Create a new tool class extending the base pattern:```typescript
    export class MyCustomTool {
    registerTools(server: McpServer): void {
    server.registerTool("my_custom_tool", {
    // Tool definition
    }, this.handleMyCustomTool.bind(this));
    }

private async handleMyCustomTool(args: any): Promise<MCPToolResult> {
// Tool implementation
}
}


2. Register the tool in `MCPDebuggerServer`:```typescript
this.myCustomTool = new MyCustomTool(config);
this.myCustomTool.registerTools(this.server);

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Add tests for new functionality
  4. Ensure all tests pass
  5. Submit a pull request

License

MIT License - see LICENSE file for details.

Supported Integrations

IDEs and Editors

  • VS Code: Full Cloud Code integration
  • IntelliJ IDEA: Cloud Code plugin support
  • Claude Desktop: Native MCP support
  • Cursor: MCP protocol support
  • Windsurf: MCP integration
  • Zed: MCP support

Cloud Platforms

  • MCP-Cloud: Enterprise deployment platform
  • Google Cloud Code: Direct IDE integration
  • Docker: Containerized deployment
  • Kubernetes: Orchestrated deployments

Workflow Automation

  • n8n: Visual workflow integration
  • Zapier: API-based integration
  • Make.com: Workflow automation
  • GitHub Actions: CI/CD integration

Programming Languages

  • TypeScript/JavaScript: Native support
  • Python: Debug adapter protocol
  • Go: Delve integration
  • Java: JDWP support
  • C#: .NET debugging
  • C/C++: GDB/LLDB support
  • PHP: Xdebug integration
  • Ruby: Ruby debugger
  • Rust: Native debugging

Support

For issues and questions:
- GitHub Issues: Report bugs and request features
- Documentation: Full API reference
- Discussions: Community support

Changelog

v0.1.0

  • Initial release with Node.js debugging support
  • Basic workspace file operations
  • Git integration
  • Test and lint execution
  • File patching with safety confirmations
  • Command execution with whitelisting
  • Comprehensive logging and error handling

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MCP Debugger B0418685 怎么安装?

在客户端按下面的安装命令接入:docker run -p 3000:3000 -e WORKSPACE_DIR=/app mcp-debugger。装完在客户端配置里引用同一个包或端点。

MCP Debugger B0418685 怎么在 Claude Desktop、Claude、VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP Debugger B0418685 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Debugger B0418685 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

MCP Debugger B0418685 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、VS Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP Debugger B0418685 能提供哪些能力?

资料显示约 21 个工具;能力标签包括 测试框架、TypeScript、Claude、代码分析。具体工具清单以官方文档为准。

MCP Debugger B0418685 需要什么运行环境?

运行时为 Docker;属于本地进程,需要在本机装好运行环境。

MCP Debugger B0418685 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。