ntop-ai-helper-mcp
Provides AI-powered diagnosis of nTop errors and supports parallel swarm diagnosis with multiple agents using OpenAI models.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ntop-ai-helper-mcp diagnose this error: Failed to generate lattice structure"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ntop-ai-helper-mcp
MCP server that helps troubleshoot nTop issues with:
AI diagnosis (
diagnose_ntop_error)20-agent parallel swarm mode (
swarm_diagnose_ntop)Screen capture (
capture_screen)Macro automation (
save_macro,list_macros,run_macro)Optional direct terminal execution (
run_terminal_command)
Quick Start
cd "$HOME\Documents\ntop-ai-helper-mcp"
npm install
npm run buildRun directly:
npm startRun in dev mode:
npm run devRelated MCP server: Error Debugging MCP Server
Environment Variables
Copy .env.example to .env and set values:
OPENAI_API_KEY(required for real AI diagnosis/swarm)OPENAI_MODEL(default:gpt-5.2)ENABLE_COMMAND_TOOL(falseby default; set totrueto allow shell command tool)
MCP Client Config Example
Use the built server file as the MCP command target:
{
"mcpServers": {
"ntop-ai-helper": {
"command": "node",
"args": [
"C:\\Users\\sohum\\Documents\\ntop-ai-helper-mcp\\dist\\server.js"
],
"env": {
"OPENAI_API_KEY": "YOUR_KEY_HERE",
"OPENAI_MODEL": "gpt-5.2",
"ENABLE_COMMAND_TOOL": "false"
}
}
}
}Tools
capture_screenInputs:
label?Output: file path to PNG in
captures/
list_macrosInputs: none
Output: all macros from
data/macros.json
save_macroInputs:
name,description?,steps[]Step types:
sleep:{ "type": "sleep", "ms": 500 }sendKeys:{ "type": "sendKeys", "keys": "^l" }command:{ "type": "command", "command": "dir" }
run_macroInputs:
name,dryRun?Executes macro step-by-step and returns a run report
diagnose_ntop_errorInputs:
errorText,context?,goal?Uses OpenAI if available; otherwise local fallback heuristics
swarm_diagnose_ntopInputs:
errorText,context?,goal?,agentCount?Runs up to 40 agents in parallel (default 20), plus final synthesis
run_terminal_commandInputs:
command,cwd?,timeoutMs?Disabled by default for safety
Notes
Screen capture and
sendKeysare Windows-oriented.Macro steps are intentionally explicit for predictable automation.
If you want stricter safety, keep
ENABLE_COMMAND_TOOL=false.
Available Tools
7 toolscapture_screenB
Capture the current primary screen and save a PNG under ./captures.
Inputs: label.
diagnose_ntop_errorB
Diagnose an nTop error. Uses OpenAI if OPENAI_API_KEY is set; otherwise returns a local fallback diagnosis.
Inputs: errorText (required), goal, context.
list_macrosA
List available automation macros.
Inputs: no named parameters.
run_macroC
Run a saved macro by name.
Inputs: name (required), dryRun.
run_terminal_commandA
Execute a terminal command for power-user automation. Disabled by default; set ENABLE_COMMAND_TOOL=true to allow.
Inputs: command (required), cwd, timeoutMs.
save_macroB
Create or update a macro with steps: sleep, sendKeys, command.
Inputs: name (required), steps (required), description.
swarm_diagnose_ntopA
Run a multi-agent nTop diagnosis swarm. Defaults to 20 agents in parallel and returns each finding + synthesis.
Inputs: errorText (required), goal, context, agentCount.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes (screen capture, macro management, terminal command). The only overlap is between diagnose_ntop_error and swarm_diagnose_ntop, both for diagnosing nTop errors, but their descriptions clarify different approaches (single vs. multi-agent).
Tool names generally follow a verb_noun pattern (capture_screen, list_macros, save_macro, run_macro, diagnose_ntop_error). The name swarm_diagnose_ntop deviates by using a noun prefix, and run_terminal_command also fits the pattern, but overall the convention is consistent.
With 7 tools, the set is well-scoped for an nTop automation and diagnostics helper. Each tool serves a distinct need without redundancy or bloat, fitting comfortably in the ideal 3-15 range.
Macro lifecycle is well covered (list, save/update, run), and diagnosis has two options. Minor gaps exist, such as no delete macro or ability to stop a running macro, but the core workflows for automation and error handling are present.
Related MCP Connectors
Finds what's broken in your product, explains why, and fixes it from your agent.
Voice-powered bug reporting with 13 MCP tools. Record bugs by talking; let AI find and fix them.
A flock of AI users tests your deployed app and reports where real people get stuck, with fixes.
Bug tracking for AI agents: session replay, console/network logs, repro packs, test plans, evidence.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to capture and analyze screen content across multi-monitor setups with smart image optimization. Provides screenshot capabilities and detailed monitor information for visual debugging, UI analysis, and desktop assistance.-
- AlicenseCqualityDmaintenanceProvides intelligent error detection and debugging capabilities across multiple programming languages with real-time monitoring of build, lint, runtime, console, and test errors. Offers AI-enhanced error analysis with automated resolution suggestions and context-aware debugging.2MIT
- AlicenseNot gradedqualityDmaintenanceCaptures comprehensive context about development issues and facilitates human assistance through structured API-based help requests.ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to diagnose, troubleshoot, and manage PC settings on Windows, macOS, and Linux through natural language commands.GPL 3.0