Provides AI coding assistants with diagnostic data about local development environments, including port conflicts, logs, and git state.
Also known as loxhness/devpulse-mcp, devpulse-mcp
- Stars
- 2
- Tools
- 3
- Downloads, 30 days
- —
- Latest version
- 0.1.3
- Last commit
- Nov 12, 2026
- License
- MIT
What is devpulse MCP?
devpulse provides AI coding assistants with diagnostic data about local development environments, including port conflicts, logs, and git state. It exposes 3 tools, such as get_session_snapshot, get_recent_errors, get_running_services.
Summary generated from the project's README
About devpulse MCP server
Giving AI coding assistants visibility into your local development environment is what devpulse enables. While assistants can read your source code, they often lack awareness of your terminal, such as whether a dev server crashed, if a port is occupied by another project, or if you are currently in the middle of a git rebase. This MCP server provides that missing context by delivering diagnostic data directly to the assistant.
Developers can use this tool locally on Linux, macOS, or Windows with zero configuration required. It works with clients like Claude Desktop, Cursor, VS Code, and Claude Code. The server runs entirely on your machine without making network requests, ensuring privacy by redacting secrets from log files before they reach the assistant. It supports various ecosystems including JavaScript, TypeScript, Python, .NET, Go, and Rust.
Through specific tools like get_session_snapshot, get_recent_errors, and get_running_services, the assistant can identify port conflicts, check for missing dependencies, detect runtime mismatches, and find merge conflicts. It provides a verdict on the likely cause of a failure along with a suggested fix.
What you can do with it
- 1Resolve port conflictsAsk your assistant to find out why your development server will not start due to an address in use error.
- 2Debug server crashesHave the AI analyze recent error logs and stack traces to determine why a service stopped running.
- 3Audit git and dependency stateAsk the assistant to check for uncommitted files, merge conflicts, or missing node_modules.
Written from the project's README. Every use case is checked against a quote from it.
How to install devpulse MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall devpulse MCP in Claude Code
$ claude mcp add devpulse-mcp -- npx -y devpulse-mcpInstall devpulse MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"devpulse-mcp": {
"command": "npx",
"args": [
"-y",
"devpulse-mcp"
]
}
}
}Install devpulse MCP in VS Code
.vscode/mcp.json
{
"servers": {
"devpulse-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"devpulse-mcp"
]
}
}
}Install devpulse MCP in VS Code CLI
$ code --add-mcp '{"name":"devpulse-mcp","type":"stdio","command":"npx","args":["-y","devpulse-mcp"]}'Install devpulse MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"devpulse-mcp": {
"command": "npx",
"args": [
"-y",
"devpulse-mcp"
]
}
}
}Install devpulse MCP in Codex
$ codex mcp add devpulse-mcp -- npx -y devpulse-mcpInstall devpulse MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.devpulse-mcp] command = "npx" args = ["-y", "devpulse-mcp"]
Install devpulse MCP in Gemini CLI
$ gemini mcp add -s user devpulse-mcp npx -- -y devpulse-mcpInstall devpulse MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"devpulse-mcp": {
"command": "npx",
"args": [
"-y",
"devpulse-mcp"
]
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for devpulse-mcp 0.1.3 in an isolated container with no network and no keys. It answered and listed 3 tools.
devpulse MCP tools 3
Read from the server with tools/listget_session_snapshotRead-onlyDiagnoses the user's local dev environment in one call: health verdict with the likely cause and a suggested fix, framework, git state (branch, uncommitted and conflicted files), dev server ports and who holds them, the 10 most recent log errors, and runtime versions. Call this first whenever the user reports something broken, before asking them what's wrong. Use the other tools only to dig deeper.
get_recent_errorsRead-onlyReturns ERROR and WARN entries from the project's .log files (logs/, log/ and the project root), with stack traces, timestamps and repeat counts. Secrets are redacted. Use this when the snapshot shows errors and you need more than its 10 most recent, or the full stack traces.
get_running_servicesRead-onlyChecks the ports this project's dev server should use (read from its config, or framework defaults) and reports which are listening, the process holding each, and whether that process belongs to this project. Use this to confirm a port conflict or check whether the dev server came back up after a restart, without rerunning the full snapshot.
Configuration
DEVPULSE_PROJECT_DIRDefault project folder to inspect when the client doesn't provide workspace roots
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachableloxhness/devpulse-mcp is public and reachablegithub.com/loxhness/devpulse-mcp ↗Pass
- Package names this repository as its sourcedevpulse-mcp names loxhness/devpulse-mcp as sourcenpmjs.com/package/devpulse-mcp ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for devpulse-mcpnpmjs.com/package/devpulse-mcp/v/0.1.3#provenance ↗Pass
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-12github.com/loxhness/devpulse-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from devpulse-mcpPass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubYour AI coding assistant can read your code. devpulse lets it see your dev environment.
Why
Your assistant can't see your terminal. It doesn't know your dev server crashed, that another project is squatting on port 3000, or that you're halfway through a rebase with conflicts. So it asks you, and you copy and paste.
devpulse is an MCP server that answers all of that in one tool call, and returns a verdict with the likely cause and a suggested fix.
- Finds port conflicts and names the culprit: which process holds your port, its pid, and the folder it was started from.
- Reads your logs: recent errors with stack traces, repeat counts and timestamps, with secrets redacted.
- Checks the rest of your setup: git state, merge conflicts, missing dependencies and runtime versions.
- Zero config: no API key, no account, nothing to set up. Runs locally on Linux, macOS and Windows.
Quick start
| Client | Install |
|---|---|
| Claude Code | /plugin install devpulse --marketplace loxhness/devpulse-mcp (adds a /devpulse:diagnose skill)or claude mcp add devpulse -- npx -y devpulse-mcp |
| Cursor | One-click install |
| VS Code | One-click install |
| Claude Desktop | Download devpulse.mcpb and double-click it, then pick a default project folder in its settings |
| Anything else (Windsurf, Cline, Zed, ...) | Add the config below |
{
"mcpServers": {
"devpulse": {
"command": "npx",
"args": ["-y", "devpulse-mcp"]
}
}
}
Requires Node 18 or later. Then ask your assistant what's wrong; it calls devpulse on its own.
What your assistant sees
Real output for a Next.js project whose dev server won't start:
{
"diagnosis": {
"health": "broken",
"primary_issue": "Port conflict: another process is using this project's dev server port",
"secondary_signals": ["Port 3000 is held by node (pid 1576), started from /home/you/old-app"],
"suggested_action": "Stop the other process (it belongs to a different directory) or run this dev server on a different port",
"confidence": "high"
},
"session": {
"project": "my-app",
"framework": "nextjs",
"git": { "branch": "feat/auth", "uncommitted_files": 5, "conflicted_files": 0, "last_commit_message": "Add login form" }
},
"services": {
"running": [{ "port": 3000, "pid": 1576, "name": "node", "process_cwd": "/home/you/old-app", "owned_by_project": false }]
},
"recent_errors": [
{
"time": "2m ago",
"level": "ERROR",
"message": "Error: listen EADDRINUSE: address already in use :::3000",
"stack": ["at Server.setupListenHandle [as _listen2] (node:net:1872:16)"],
"source": "logs/dev.log",
"count": 1
}
],
"env": { "node": "22.11.0", "package_manager": "pnpm" }
}
Shortened. The full snapshot also includes process start times, ports that couldn't be checked, ahead/behind counts, runtime versions and the log files scanned.
What it diagnoses
| Problem | How devpulse knows |
|---|---|
| Port conflict | A recent EADDRINUSE, or the dev port held by a process started from a different folder |
| Old instance still running | The process on the port belongs to this project and started before the error |
| Dev server crashed | Nothing on the expected port, and errors in the last hour of logs |
| Dev server not started | Nothing on the expected port, and no errors |
| Failed to start, port free now | EADDRINUSE was logged, but the port has since been released |
| Merge conflicts | Conflicted files, or a merge or rebase in progress |
| Dependencies not installed | package.json has dependencies but there's no node_modules |
| Runtime mismatch | Installed Node or Python differs from .nvmrc, .node-version, engines or .python-version |
| Errors while running | The server is up, but errors were logged |
Tools
| Tool | Use it for |
|---|---|
get_session_snapshot |
Everything above in one call. Assistants call this first. |
get_recent_errors |
More than the snapshot's 10 newest errors, with full stack traces (limit 1 to 200) |
get_running_services |
Re-checking ports after a restart, without the full snapshot |
All three are read-only and take an optional cwd.
Supported projects
| Language | Detected from | Frameworks |
|---|---|---|
| JavaScript / TypeScript | package.json |
Next.js, Nuxt, SvelteKit, Astro, Remix, Angular, Vite, NestJS, Fastify, Express, Create React App |
| Python | pyproject.toml, requirements.txt, Pipfile, manage.py |
FastAPI, Django, Flask |
| .NET | *.csproj, *.sln |
ASP.NET Core (ports from Properties/launchSettings.json) |
| Go, Rust | go.mod, Cargo.toml |
Any |
Ports come from your own config when devpulse can find them (--port, -p or PORT= in your dev script, PORT in .env, server.port in vite.config, launchSettings.json), and from framework defaults otherwise.
- The
cwdthe assistant passes, if any - The workspace folder your editor reports over MCP (roots)
DEVPULSE_PROJECT_DIR, if set (the Claude Desktop extension sets this from its settings)- The folder the server was launched from (Claude Code launches it in your project)
- Errors come from log files. Most dev servers print to the terminal instead of a log file, so if your project has no
.logfiles,recent_errorswill be empty. Port, git and dependency checks still work. Terminal capture is planned for 0.2. - Ownership and start times aren't checked on Windows. Ports and processes are still detected, but devpulse can't tell whose process it is, so it reports conflicts at lower confidence.
- Runtime versions are read from the environment devpulse runs in, which can differ from your shell if you use nvm or pyenv. Mismatches are reported as signals, not verdicts.
Privacy and security
- Runs entirely on your machine and makes no network requests.
- Read-only: devpulse never changes files, stops processes or runs your code.
- Secrets (API keys, tokens, passwords and credentials in URLs) are redacted from log lines before your assistant sees them.
- Every npm release is built and published from GitHub Actions with provenance.
Development
npm install
npm test # unit tests plus end-to-end tests over stdio
npm run build
CI runs on Linux, macOS and Windows with Node 18, 20 and 22. To release, run npm version patch && git push --follow-tags: the release workflow tests, publishes to npm and the MCP Registry, builds the Claude Desktop extension and creates the GitHub release from CHANGELOG.md.
Bug reports and ideas are welcome in Issues.
License
MIT © Uzair Suboor
devpulse MCP questions
How do I add devpulse MCP to Claude Code?
Run claude mcp add devpulse-mcp -- npx -y devpulse-mcp in your terminal. Add --scope user to make it available in every project.
How do I add devpulse MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does devpulse MCP provide?
It exposes 3 tools, including get_session_snapshot, get_recent_errors, get_running_services.
Does devpulse require any configuration or API keys?
No, it is zero config and requires no API key or account to set up.
Can devpulse modify my files or stop my processes?
No, the tool is read-only and does not change files, stop processes, or run your code.
What operating systems are supported?
It runs locally on Linux, macOS, and Windows.