MCP Server Manager for Cursor

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.

FAQ from MCP Server Manager for Cursor

What is an MCP server?

An MCP server acts as a bridge between Cursor and external services (like Jira, Slack, Confluence) by exposing standardized tools that Cursor can call, enabling retrieval of issues, page search, or messaging directly from the IDE.

How do I add a new MCP server?

Copy an example configuration file from examples/ into servers/, rename it (e.g., mcp-myservice.config.ts), edit fields like name, type, image, args, and healthValidator, then create a corresponding .env file in servers/config/.

What are the runtime requirements?

The manager runs on Deno and uses Docker to start HTTP/SSE servers as persistent containers. STDIO servers are not run as containers persistently; Cursor launches them as needed.

Where does the manager store state?

Server status (e.g., running/stopped) is kept in data/state.json, managed automatically by the CLI. Cursor MCP configuration is updated in the global or local mcp.json file.

How does authentication work for servers?

Credentials and sensitive settings are stored in individual .env files per server (e.g., servers/config/mcp-myservice.env). These files should be added to .gitignore to prevent accidental commits. No other auth transport is described.