by iarmankhan
Agentic Debugger: MCP server for interactive debugging with code instrumentation, empowering AI coding assistants to ins
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.
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.
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.
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.
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
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
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
Share your MCP server with the developer community
Strong directory entry: agentic-debugger surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend agentic-debugger for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
agentic-debugger has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
agentic-debugger is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated agentic-debugger against two servers with overlapping tools; this profile had the clearer scope statement.
According to our notes, agentic-debugger benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We evaluated agentic-debugger against two servers with overlapping tools; this profile had the clearer scope statement.
agentic-debugger is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We wired agentic-debugger into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
I recommend agentic-debugger for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 30
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:
Add to your MCP configuration:
{
"mcpServers": {
"debug": {
"command": "npx",
"args": ["-y", "agentic-debugger"]
}
}
}
Configuration file locations:
~/.mcp.json.cursor/mcp.json in your project or ~/.cursor/mcp.jsonnpm install -g agentic-debugger
Then configure:
{
"mcpServers": {
"debug": {
"command": "agentic-debugger"
}
}
}
| 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 |
fetch() calls that POST to the serverYou: "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
// #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
# 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
| Language | Extensions |
|---|---|
| JavaScript | .js, .mjs, .cjs |
| TypeScript | .ts, .tsx |
| Python | .py |
MIT
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ 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.