AI SummaryAn MCP server that provides unified control over multiple development servers (Django, Vue, Celery, etc.) through a TUI interface, enabling LLM-assisted development workflows in Copilot. Ideal for developers managing complex local environments who want programmatic server control integrated with AI assistants.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "devserver-mcp — Copilot Instructions" prompt rules to my project. Repository: https://github.com/Uninen/devserver-mcp Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
MCP server and a unified TUI for managing dev servers + Playwright
Project: Devserver MCP
This project is a Model Context Protocol (MCP) server that manages development servers (Django, Vue, Celery, etc.) for LLM-assisted development workflows. Provides programmatic control over multiple development servers through a unified interface with a beautiful TUI.
Quick Reference
• Dependency and environment management: uv • uv add [package] -- add dependency • uv add --dev [package] -- add dev dependency • uv run [command in .venv context] -- run a command in the project environment • pyproject.toml -- Python project configuration • Tests: • Run with: use your run_tests tool or uv run pytest • In tests/ • Use Ruff for linting and formatting: • uv run ruff check --fix path/to/file.py -- fix all fixable linting errors • uv run ruff format path/to/file.py -- format • Test the server implementation using the test app (see details below): uv run devservers
Coding Guidelines
• Python 3.13+, type hints, PEP 8 • Handle errors explicitly • Never add any comments or doctsrings unless asked to • Always follow security best practices. Never introduce code that exposes or logs secrets and keys • Always lint and format all the code you write using Ruff
Testing Guidelines
• Adhere to the general testing guidelines in docs/writing_tests.md • Write meaningful tests, not coverage fillers • Always use pytest functions, never use classes • When creating or fixing tests, always run the full test suite to make sure all tests pass
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts