AMS Development MCP Servers
MCP servers for real-time development monitoring and interactive pair programming.
README
AMS Development MCP Servers
MCP servers for real-time development monitoring and interactive pair programming
Overview
A suite of Model Context Protocol (MCP) servers designed to enhance AI-assisted development workflows. These servers enable AI assistants like Claude Code to actively monitor development processes, inspect running applications, and participate in interactive debugging sessions.
Packages
This monorepo contains four interconnected MCP servers:
@ams-dev/process-manager · npm
Monitor and control development processes (nx serve, npm run, etc.)
- Start, stop, and restart processes
- Stream and filter process logs in real-time
- Send input to interactive processes
- Pattern-based monitoring for errors and warnings
@ams-dev/docker-manager · npm
Control and inspect Docker containers
- List, start, stop, and restart containers
- Execute commands inside containers
- Stream container logs
- Inspect container configuration and state
@ams-dev/dev-watcher · npm
Real-time error detection and pattern matching across all development sources
- Aggregate logs from processes and containers
- Regex pattern matching for errors and warnings
- Alert deduplication and severity classification
- Integration with browser console logs
@ams-dev/browser-inspector · npm
Browser automation, inspection, monitoring, and performance analysis using Puppeteer
- Navigate and interact with web pages (click, type, wait for elements)
- Monitor console logs and network requests in real-time
- Capture screenshots and extract page content
- Execute custom JavaScript in browser context
- Performance metrics (load times, FCP, resource counts)
- Automated accessibility audits
- Cookie and localStorage management
Quick Start
Installation
# Install all packages globally
npm install -g @ams-dev/process-manager @ams-dev/docker-manager @ams-dev/dev-watcher @ams-dev/browser-inspector
# Or use with npx (no installation required)
npx @ams-dev/process-manager
Configuration
Add to your Claude Code MCP configuration (~/.config/claude/mcp.json):
{
"mcpServers": {
"process-manager": {
"command": "npx",
"args": ["-y", "@ams-dev/process-manager"]
},
"docker-manager": {
"command": "npx",
"args": ["-y", "@ams-dev/docker-manager"]
},
"dev-watcher": {
"command": "npx",
"args": ["-y", "@ams-dev/dev-watcher"]
},
"browser-inspector": {
"command": "npx",
"args": ["-y", "@ams-dev/browser-inspector"]
}
}
}
Use Cases
NX Monorepo Development
Claude: "I'll start the admin and products services for you"
- Starts both services with process-manager
- Monitors for compile errors
- Reports when servers are ready
Docker-based Development
Developer: "Set up the local environment"
Claude: "Starting your database containers"
- Starts PostgreSQL and Redis containers
- Checks container health
- Reports when services are ready
Interactive Debugging
Developer: "Why is the API slow?"
Claude:
- Checks API process logs for slow queries
- Inspects PostgreSQL container logs
- Reports findings with specific line references
Development
This project uses PNPM workspaces for monorepo management.
# Clone the repository
git clone https://github.com/mastoica/vibecoding-mcp-servers.git
cd vibecoding-mcp-servers
# Install dependencies
pnpm install
# Build all packages
pnpm build
# Run tests
pnpm test
Documentation
- Getting Started (coming soon)
- Installation Guide (coming soon)
- Configuration (coming soon)
- Examples (coming soon)
Requirements
- Node.js >= 18.0.0
- PNPM >= 8.0.0
- Docker (optional, for docker-manager)
Contributing
Contributions are welcome! Please read our contributing guidelines before submitting PRs.
License
MIT © mastoica
Roadmap
- [x] Repository setup
- [ ] Process Manager MCP (v0.1.0)
- [ ] Docker Manager MCP (v0.1.0)
- [ ] Dev Watcher MCP (v0.1.0)
- [ ] Complete documentation
- [ ] CI/CD pipeline
- [ ] Publish to npm
Status: 🚧 Work in Progress - Initial development phase
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.