
DevServer MCP
Monitors development server logs in real-time and provides Claude with immediate error notifications via Server-Sent Events. Intelligently parses TypeScript, Svelte, and Vite errors with severity classification and file correlation.
README
DevServer MCP
An MCP server that monitors development server logs in real-time, categorizes errors by type and severity, and provides Claude Code with immediate error notifications via Server-Sent Events (SSE).
DevServer MCP:
- Real-time notifications: Instant error alerts via SSE transport
- Intelligent parsing: Recognizes TypeScript, Svelte, Vite error patterns
- Error correlation: Links errors to recent file changes
- Severity classification: Critical vs warning vs info
- Multiple client support: Connect multiple Claude Code instances simultaneously
- AI integration: Claude Code receives structured error data instead of raw logs
Quick Start
# Install and build
pnpm install && pnpm build
# Start monitoring with SSE server (uses default port 9338)
node dist/server.js --monitor pnpm run dev
# Connect Claude Code (port stays consistent across restarts)
claude mcp add --transport sse devserver-mcp http://127.0.0.1:9338/sse
Now Claude Code receives immediate notifications when errors occur!
Core Workflow
Traditional debugging:
- Notice something broken → 2. Scroll through terminal → 3. Find relevant error → 4. Google it
With DevServer MCP:
- Error occurs → 2. Instant notification in Claude Code → 3. Get categorized errors with file locations → 4. Ask "How do I fix this?"
MCP Tools
get_dev_server_status
- Current server health and error countsget_error_summary
- Errors grouped by type/severityget_error_history
- Chronological error list with filteringget_file_errors
- Errors for a specific filesuggest_monitoring_setup
- Project-specific setup recommendations
Port Configuration
Default Port (9338):
# Start with default port
node dist/server.js --monitor pnpm run dev
# Connect Claude Code
claude mcp add --transport sse devserver-mcp http://127.0.0.1:9338/sse
Custom Port Per Project:
# Frontend project on port 9339
node dist/server.js --port 9339 --monitor pnpm run dev
# Backend project on port 9340
node dist/server.js --port 9340 --monitor npm run dev:api
# Connect to specific projects
claude mcp add --transport sse frontend-devserver http://127.0.0.1:9339/sse
claude mcp add --transport sse backend-devserver http://127.0.0.1:9340/sse
Benefits:
- ✅ Consistent ports - same port every restart, no need to re-add MCP server
- ✅ Per-project ports - run multiple projects simultaneously
- ✅ Conflict detection - helpful error messages if port is already in use
Architecture
SSE-Based Real-Time System:
- Monitor mode (
--monitor
): Spawns dev server, parses logs, broadcasts errors via SSE - HTTP server: Serves
/sse
endpoint for Claude Code connections on specified port - Error buffering: Maintains recent error history for newly connected clients
- Multi-client support: Multiple Claude Code instances can connect simultaneously
Real-time error streaming means Claude Code gets notified within 1-2 seconds of any dev server issue.
Error Categories
Built-in patterns for:
- TypeScript compilation errors
- Svelte component warnings
- Vite build failures
- Network/API errors
- Runtime JavaScript errors
- Accessibility issues
Configuration
Create devserver-mcp.config.json
:
{
"processPatterns": ["pnpm run dev", "npm run dev"],
"historyLimit": 1000,
"correlationWindow": 5000,
"watchPaths": ["src", "lib"],
"excludePaths": ["node_modules", ".git"],
"patterns": [
{
"name": "custom-error",
"pattern": "CUSTOM: (.+)",
"category": "runtime",
"severity": "critical"
}
]
}
Development
pnpm install # Install deps
pnpm build # Build project
pnpm dev # Watch mode
pnpm test # Run tests
pnpm typecheck # Type checking
Troubleshooting
Connection Failed
# Check if monitoring server is running
ps aux | grep "node.*server.js"
# Restart monitoring server (default port 9338)
node dist/server.js --monitor pnpm run dev
# Verify connection
claude mcp add --transport sse devserver-mcp http://127.0.0.1:9338/sse
Port Already in Use
# Error: Port 9338 is already in use!
# Solution: Use a different port
node dist/server.js --port 9339 --monitor pnpm run dev
# Then connect with the new port
claude mcp add --transport sse devserver-mcp http://127.0.0.1:9339/sse
No Real-Time Notifications
# Check MCP connection status
claude mcp list
# Remove and reconnect if needed
claude mcp remove devserver-mcp
claude mcp add --transport sse devserver-mcp http://127.0.0.1:9338/sse
Multiple Projects
# Each project should use a different port
# Project A
node dist/server.js --port 9338 --monitor pnpm run dev
# Project B
node dist/server.js --port 9339 --monitor npm run dev
# Connect both in Claude Code with different names
claude mcp add --transport sse project-a http://127.0.0.1:9338/sse
claude mcp add --transport sse project-b http://127.0.0.1:9339/sse
License
MIT
推荐服务器

Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。