runtime-mcp-server
Allows tailing stdout/stderr and crash logs from Docker-based dev servers so AI agents can inspect stack traces and runtime errors directly.
Click on "Install 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., "@runtime-mcp-serverCheck what process is using port 3000 and tail its logs."
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.
Runtime Diagnostic MCP Server (runtime-mcp-server)
A local Model Context Protocol (MCP) server that provides AI coding agents (like OpenAI Codex CLI) with real-time runtime diagnostics, process monitoring, and log analysis for local development environments.
🎯 Purpose
AI coding agents are great at inspecting static code, but blind to runtime execution state. This server bridges that gap by giving AI agents programmatic, read-only tools to observe running processes, analyze crash logs, inspect active ports, and monitor system resources.
Related MCP server: Harbor MCP Server
🛠️ Core Tools (v1 Features)
tail_app_logsDescription: Reads and tails recent stdout/stderr streams or crash logs from active background dev servers (
npm run dev,python,docker).Goal: Hands raw stack traces to Codex automatically without manual copy-pasting.
inspect_portsDescription: Scans active local network ports (e.g., 3000, 8080) and identifies occupying process IDs (PIDs).
Goal: Automatically resolves
EADDRINUSE/ "Port already in use" errors and can safely signal zombie processes.
get_process_metricsDescription: Monitors CPU and RAM usage for specific local application processes.
Goal: Helps Codex detect infinite loops, memory leaks, and runaway background scripts in real time.
capture_network_errorsDescription: Inspects local failed HTTP/gRPC responses, CORS headers, and status codes.
Goal: Pinpoints root causes for broken frontend-to-backend local API connections.
🏗️ Technical Stack
Language: TypeScript / Node.js
Protocol: Model Context Protocol (MCP) via
@modelcontextprotocol/sdkTransport: Standard Input/Output (
stdio)System APIs:
child_process,fs/promises,psutil/ system process utilities
🚀 Getting Started
Install dependencies and compile the TypeScript source:
npm install
npm run buildStart the MCP server:
npm startThe initial server connects over stdio and is ready for diagnostic tools to be added.
🚀 Codex CLI Integration
Configured in ~/.codex/config.json (or Codex client settings):
{
"mcpServers": {
"runtime-diagnostics": {
"command": "node",
"args": ["/Users/USERNAME/Documents/Codex/runtime-mcp-server/build/index.js"]
}
}
}đź“‹ Development Roadmap
Initialize TypeScript &
@modelcontextprotocol/sdkprojectImplement
inspect_portstoolImplement
tail_app_logstoolImplement
get_process_metricstoolAdd integration tests with Codex CLI
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceGives AI agents real-time access to system metrics, process management, and container orchestration.
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to discover, configure, and manage local development servers. Provides tools for app registration, port allocation, lifecycle control, and log access without manual config editing.338MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM clients to inspect local dev environments—Docker container health, pnpm workspace integrity, and stuck process detection—without manual terminal copy-pasting.MIT
- AlicenseAqualityBmaintenanceProvides AI coding agents with structured, evidence-based diagnostics about the local development environment, detecting tech stack, runtime mismatches, dependency state, services, ports, and Git status without exposing secrets or using network calls.10Apache 2.0
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
Watchdog for unattended AI agents: agent health, alerts, run reports with evidence and cost.
AI agent run monitoring with incident replay and SLA receipts.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/becketthayes/runtime-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server