Skip to main content
Glama
Madiocre

DevEnv Doctor MCP

by Madiocre

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tasks
{
  "list": {},
  "cancel": {},
  "requests": {
    "tools": {
      "call": {}
    }
  }
}
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": true,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

Sanity check — returns pong plus the current server time.

check_docker_statusA

Checks whether a given container is running and whether its expected port is actually bound on the host.

check_pnpm_workspaceA

Validates pnpm-workspace.yaml, detects orphaned packages, dead glob patterns, lockfile staleness, and missing package manager pin.

diagnose_stuck_processC

Finds processes bound to a given port and flags likely zombie/hung states.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Health ChecksCurrent health status of all registered health checks
Widget ExamplesProvides metadata and examples for all registered UI widgets

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct concern: ping for liveness, Docker container status, pnpm workspace validation, and process diagnosis. No two tools overlap in purpose, so an agent can easily select the right one.

Naming Consistency4/5

Three tools use a verb_noun pattern (check_docker_status, check_pnpm_workspace, diagnose_stuck_process), but 'ping' deviates by using a standalone verb without a prefix. This is a minor inconsistency, but the naming remains intuitive.

Tool Count5/5

With only 4 tools, the server is tightly scoped for a development environment diagnostics tool. Each tool provides a specific health check, and the count feels appropriate without being too thin or overloaded.

Completeness3/5

The tools cover several common dev environment issues (Docker, pnpm, stuck processes), but the broad 'DevEnv Doctor' purpose suggests missing checks like system resource monitoring or package manager version validation. These are notable gaps but agents can work around them.

Maintenance

ActivityStale
ResponsivenessNo issues