agentic-debugger▌
by iarmankhan
Agentic Debugger: MCP server for interactive debugging with code instrumentation, empowering AI coding assistants to ins
An MCP (Model Context Protocol) server that enables interactive debugging with code instrumentation for AI coding assistants. Inspired by Cursor's debug mode.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / AI coding assistants debugging runtime issues
- / Developers using Claude, Cursor, or similar tools
- / Troubleshooting variable state in running code
- / Interactive debugging without traditional debugger setup
capabilities
- / Insert debug logging at specific code lines
- / Capture variable values during code execution
- / Start HTTP server for collecting debug logs
- / Remove debug instruments cleanly from code
- / Read and analyze captured runtime data
- / Support JavaScript, TypeScript, and Python debugging
what it does
Enables AI coding assistants to debug code by inserting temporary logging instruments that capture variable values at runtime. Works with JavaScript, TypeScript, and Python across multiple AI coding tools.
about
agentic-debugger is a community-built MCP server published by iarmankhan that provides AI assistants with tools and capabilities via the Model Context Protocol. Agentic Debugger: MCP server for interactive debugging with code instrumentation, empowering AI coding assistants to ins It is categorized under developer tools. This server exposes 7 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install agentic-debugger in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
agentic-debugger is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
agentic-debugger
An MCP (Model Context Protocol) server that enables interactive debugging with code instrumentation for AI coding assistants. Inspired by Cursor's debug mode.
Works with any MCP-compatible AI coding tool:
- Claude Code
- Cursor
- Windsurf
- Cline
- GitHub Copilot
- Kiro
- Zed
- And more...
Features
- Live code instrumentation - Inject debug logging at specific lines
- Variable capture - Log variable values at runtime
- Multi-language support - JavaScript, TypeScript, and Python
- Browser support - CORS-enabled for browser JS debugging
- Clean removal - Region markers ensure instruments are fully removed
Installation
Using npx (recommended)
Add to your MCP configuration:
{
"mcpServers": {
"debug": {
"command": "npx",
"args": ["-y", "agentic-debugger"]
}
}
}
Configuration file locations:
- Claude Code:
~/.mcp.json - Cursor:
.cursor/mcp.jsonin your project or~/.cursor/mcp.json - Other tools: Check your tool's MCP documentation
Global install
npm install -g agentic-debugger
Then configure:
{
"mcpServers": {
"debug": {
"command": "agentic-debugger"
}
}
}
Available Tools
| Tool | Description |
|---|---|
start_debug_session | Start HTTP server for log collection |
stop_debug_session | Stop server and cleanup |
add_instrument | Insert logging code at file:line |
remove_instruments | Remove debug code from file(s) |
list_instruments | Show all active instruments |
read_debug_logs | Read captured log data |
clear_debug_logs | Clear the log file |
How It Works
- Start session - Spawns a local HTTP server (default port 9876)
- Add instruments - Injects
fetch()calls that POST to the server - Reproduce bug - Run your code, instruments capture variable values
- Analyze logs - Read the captured data to identify issues
- Cleanup - Remove all instruments and stop the server
Debug Workflow Example
You: "Help me debug why the total is NaN"
AI Assistant:
1. Starts debug session
2. Reads your code to understand the logic
3. Adds instruments at suspicious locations
4. "Please run your code to reproduce the issue"
You: *runs code* "Done"
AI Assistant:
5. Reads debug logs
6. "I see `discount` is undefined at line 15..."
7. Removes instruments
8. Fixes the bug
9. Stops debug session
Instrument Examples
JavaScript/TypeScript
// #region agentic-debug-abc123
fetch('http://localhost:9876/log', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
id: 'abc123',
location: 'cart.js:15',
timestamp: Date.now(),
data: { total, discount, items }
})
}).catch(() => {});
// #endregion agentic-debug-abc123
Python
# region agentic-debug-abc123
try:
import urllib.request as __req, json as __json
__req.urlopen(__req.Request(
'http://localhost:9876/log',
data=__json.dumps({
'id': 'abc123',
'location': 'cart.py:15',
'timestamp': __import__('time').time(),
'data': {'total': total, 'discount': discount}
}).encode(),
headers={'Content-Type': 'application/json'}
))
except: pass
# endregion agentic-debug-abc123
Supported Languages
| Language | Extensions |
|---|---|
| JavaScript | .js, .mjs, .cjs |
| TypeScript | .ts, .tsx |
| Python | .py |
Requirements
- Node.js >= 18.0.0
- An MCP-compatible AI coding assistant
License
MIT
FAQ
- What is the agentic-debugger MCP server?
- agentic-debugger is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for agentic-debugger?
- This profile displays 30 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.6★★★★★30 reviews- ★★★★★Chaitanya Patil· Dec 24, 2024
Strong directory entry: agentic-debugger surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Liam Nasser· Dec 20, 2024
I recommend agentic-debugger for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Sakura Taylor· Nov 19, 2024
agentic-debugger has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Piyush G· Nov 15, 2024
agentic-debugger is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Yusuf Martinez· Nov 11, 2024
We evaluated agentic-debugger against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Sakura Liu· Oct 10, 2024
According to our notes, agentic-debugger benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Shikha Mishra· Oct 6, 2024
We evaluated agentic-debugger against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Olivia Agarwal· Oct 2, 2024
agentic-debugger is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Yash Thakker· Sep 25, 2024
We wired agentic-debugger into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Kiara Sethi· Sep 25, 2024
I recommend agentic-debugger for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 30