What is MCP Server Manager for Cursor?
An MCP (Model Context Protocol) workspace manager for Cursor that simplifies managing multiple MCP servers in local development environments. It provides a consistent CLI for starting, stopping, updating, and checking the status of all configured servers at once or individually, and automatically updates Cursor’s global or local mcp.json configuration file.
How to use MCP Server Manager for Cursor?
Define each MCP server as a TypeScript configuration file in the servers/ directory using templates from examples/. Set per‑server environment variables in .env files under servers/config/. Then run CLI commands via deno task (e.g., deno task start, deno task stop, deno task status). Optional --server=<name> flag targets a specific server, and --dry-run previews Cursor config changes.
Key features of MCP Server Manager for Cursor
- Centralized CLI for starting, stopping, and updating MCP servers
- Supports both HTTP/SSE and STDIO server types
- Automatically manages Cursor
mcp.json configuration
- Per‑server health validation with
healthValidator configuration
- Dry‑run mode to preview Cursor config changes
- Real‑time log streaming and status monitoring
Use cases of MCP Server Manager for Cursor
- A developer runs multiple MCP servers (Jira, Slack, Confluence) and wants a single command to start or stop them all.
- A team maintains shared MCP server definitions in a forked repository with secured credentials.
- A developer needs to quickly update Docker images for all their MCP servers without manual
docker pull.
- An administrator validates that all active MCP servers are healthy after starting their workspace.
コメント