What information does devpulse report?

It reports project and framework details, Git state, running and missing services, recent errors, Node and package-manager information, and a diagnostic assessment.

Where does devpulse run?

It runs entirely on the local machine, and the README states that no data leaves the computer.

Which frameworks are detected?

Next.js, Vite, Express, and FastAPI are detected automatically from package.json.

Which clients are documented?

The setup instructions document Claude Code, Cursor, Claude Desktop, and Windsurf.

Devpulse MCP

developer-toolsdiagnosticslocal-developmentdebugging

Local MCP server that gives coding assistants a diagnostic snapshot of project, services, errors, and Git state.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

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

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

devpulse inspects a local development environment and returns project details, detected frameworks, running or missing services, recent log errors, and Git state. Use it when an AI coding assistant needs current debugging context without manual copy-paste. It runs locally, requires no API key or configuration file, and redacts secrets from log output.

Use cases

Inspect the current project and development environment

Identify missing or conflicting development services

Review recent errors from local log files

Check the current Git branch and uncommitted files

Key features

Full diagnostic snapshot with health and suggested action

Recent error retrieval with secret redaction

Running and expected service detection

Automatic framework detection for Next.js, Vite, Express, and FastAPI

Git branch and uncommitted-file reporting

Capabilities & Tool Schemas (3)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Devpulse MCP.

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

Documentation Overview

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

config.json

{
  "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.

Setup

Claude Code

Terminal

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

Cursor / Claude Desktop / Windsurf

config.json

{
  "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

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

4mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Devpulse MCP

No. The README states that it requires no API key, account, or configuration file.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/tao-izm-devpulse-mcp?style=directory)](https://allmcps.com/mcp/tao-izm-devpulse-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/tao-izm-devpulse-mcp"><img src="https://allmcps.com/api/badge/tao-izm-devpulse-mcp?style=directory" alt="Devpulse MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

PricingFree

4/5 checks healthy over the last 32d

52Quality signal: Good · 52/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools28/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 26d ago via OSV.dev · devpulse-mcp (npm)

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Devpulse MCP →Install in Claude Desktop Install in Cursor Install in VS Code

Overview

Use cases

Inspect the current project and development environment

Identify missing or conflicting development services

Review recent errors from local log files

Check the current Git branch and uncommitted files

Key features

Full diagnostic snapshot with health and suggested action

Recent error retrieval with secret redaction

Running and expected service detection

Automatic framework detection for Next.js, Vite, Express, and FastAPI

Git branch and uncommitted-file reporting

Documentation Overview

devpulse

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

What your AI sees

config.json

{
  "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.

Setup

Claude Code

Terminal

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

Cursor / Claude Desktop / Windsurf

config.json

{
  "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

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

4mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.