raycast -manager

This MCP server is designed to power a Raycast-based MCP management workflow. It exposes a server-side API and tooling that lets you start, stop, and monitor MCP servers used by your Raycast workspace. Through the provided commands, you can list active MCP instances, inspect status, and perform basic lifecycle actions. The tooling focuses on enabling seamless integration with Raycast so you can trigger MCP actions directly from your Raycast workflow or UI panels.

To use it, ensure your environment can reach the MCP server and that you supply any required authentication or API keys if you have them configured. The server will expose endpoints to manage individual MCP server entries, allowing you to scale your MCP infrastructure from a single control point. Typical usage involves starting the manager, then using the Raycast UI or CLI to view status, restart services, or apply configuration changes as needed.

Prerequisites:

• Node.js (12.x or newer) and npm/yarn installed on your system
• Access to install dependencies for the server

1. Install the package

• Using npm: npm install -g raycast-mcp-server-manager
• Or using yarn: yarn global add raycast-mcp-server-manager

2)Configure environment (optional but recommended)

• Create a .env file or export environment variables: PORT=3000 RAYCAST_API_KEY=your-raycast-api-key

3)Run the server

• npm (or npx): npx raycast-mcp-server-manager
• Or run locally if you have a local clone: node server.js

4)Verify installation

• Access http://localhost:3000 (or configured port) to confirm the MCP server manager is running.
• Check status endpoints or logs to ensure MCP servers are registered and ready.

Tips and common considerations:

• If you deploy behind a proxy or firewall, ensure the configured port is accessible and not blocked.
• If you change environment variables (like API keys), restart the MCP server manager to apply them.
• Use a descriptive server name under mcpServers to avoid confusion when managing multiple MCP instances.
• Check logs for startup errors related to missing dependencies or port conflicts.
• If integrating with Raycast, consider creating a small UI panel that calls the MCP manager endpoints to perform actions (start/stop/list) directly from Raycast.
• Ensure you have proper authentication in place if exposing management endpoints publicly.