Skip to main content
Glama

devpulse

An MCP server that lets your AI coding assistant see what's actually happening in your dev environment.

When you're debugging with Claude Code or Cursor, the AI has no idea if your dev server is running, what errors just appeared in the logs, or what branch you're on. You end up copy-pasting the same context every session. devpulse fixes that with one tool call.

What your AI sees

{
  "diagnosis": {
    "health": "broken",
    "primary_issue": "Port conflict — dev server cannot start",
    "suggested_action": "Kill the process using that port or change your dev server port",
    "confidence": "high"
  },
  "session": {
    "project": "my-app",
    "framework": "nextjs",
    "branch": "feat/auth",
    "uncommitted_files": 3
  },
  "services": {
    "running": [],
    "expected_but_missing": [3000]
  },
  "recent_errors": [
    { "time": "2m ago", "level": "ERROR", "message": "EADDRINUSE :::3000" }
  ],
  "env": {
    "node": "20.11.0",
    "package_manager": "pnpm"
  }
}

Instead of asking you what's wrong, the AI already knows.

Related MCP server: AI Knowledge Center MCP

Setup

Claude Code

claude mcp add devpulse -- npx -y devpulse-mcp

Cursor / Claude Desktop / Windsurf

{
  "mcpServers": {
    "devpulse": {
      "command": "npx",
      "args": ["-y", "devpulse-mcp"]
    }
  }
}

No API key. No account. No config file.

Tools

  • get_session_snapshot — full diagnostic snapshot, call this first

  • get_recent_errors — recent errors from your log files, secrets redacted

  • get_running_services — what's on your dev ports and what's missing

Supported frameworks

Detected automatically from your package.json — Next.js, Vite, Express, FastAPI. More coming.

Privacy

Runs entirely on your machine. No data leaves your computer. API keys and secrets are automatically stripped from log output.

License

MIT

Available Tools

3 tools
get_recent_errorsA

Returns recent ERROR and WARN log entries from the detected project's log files. Deduped, timestamped, secrets redacted. Defaults to last 50 lines.

Inputs: cwd, limit.

get_running_servicesB

Lists processes running on common dev ports (3000, 4000, 5173, 8080 etc). Shows what is running and what is expected but missing.

Inputs: cwd.

get_session_snapshotA

Returns a real-time diagnostic snapshot of the current dev environment. Includes health diagnosis, running services, recent errors, git state, and environment info. Call this first to orient yourself in the user's dev session.

Inputs: cwd.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation3/5

    The tools have overlapping information: get_session_snapshot includes recent errors and running services, making it redundant with the other two. Descriptions help clarify usage order, but ambiguity remains.

    Naming Consistency5/5

    All tools follow a consistent 'get_' prefix with clear noun phrases, forming a predictable and readable pattern.

    Tool Count4/5

    Three tools is on the low side for a dev diagnostic server, but the snapshot tool consolidates key info, making the count reasonable for basic orientation.

    Completeness4/5

    The set covers errors, services, and a broad snapshot (git, env, health). Minor gaps like detailed log history or dependency checks exist, but core diagnostics are present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives your AI assistant full awareness of your local dev environment — running processes, Docker containers, git state, open ports, log files, and more.
      8 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Local-first MCP server that indexes all projects on your machine and provides coding agents with briefings about each project's stack, services, and run instructions, so they can start sessions with context across all repos. No cloud, no accounts, no telemetry.
      6 npm
      MIT