raycast

This Raycast MCP Server exposes 9 tools that integrate Raycast with an AI assistant workflow, enabling authenticated access, extension management, workflow automation, and system interactions through the MCP interface. You can invoke individual tools by passing a tool name and arguments, for example to create or execute a workflow, search for extensions, or manage Raycast authentication. The environment variables RAYCAST_API_KEY and RAYCAST_TEAM_ID are used to authorize with Raycast services where applicable.

The server supports tools such as raycast_auth for authentication workflows, raycast_extensions for managing and listing Raycast extensions, raycast_workflows for creating and executing custom automations, raycast_search for locating and launching applications or files, raycast_clipboard for clipboard history management, raycast_shortcut for triggering shortcuts, raycast_window for window behavior control, raycast_system for system-level interactions, and additional workflow tools to extend automation scenarios. Use the tools by providing a JSON payload with tool and arguments to perform specific actions, e.g. creating a morning routine workflow or validating credentials for a service.

Prerequisites:\n- Node.js 18+ (runtime for the MCP server)\n- npm (comes with Node.js)\n- Raycast installed on macOS if you plan to test Raycast-specific features locally\n\nInstallation steps:\n1) Clone the repository or download the source for the raycast-mcp-server.\n2) Navigate into the project directory:\n git clone https://github.com/ExpertVagabond/raycast-mcp-server.git\n cd raycast-mcp-server\n3) Install dependencies:\n npm install\n4) Build the project (if applicable in your setup):\n npm run build\n5) Run the server locally to test:\n npm start\n6) Configure your MCP client to point to the server, using the provided mcp_config example. For production, deploy the built dist/index.js with the appropriate environment variables.\n\nNotes:\n- Ensure RAYCAST_API_KEY and RAYCAST_TEAM_ID are available in the environment when running the server.\n- If using NPX or other distribution methods, adjust the command/args accordingly as per deployment method.

Tips and common issues:\n- Ensure Node.js version compatibility (18+) as required by the project.\n- When deploying, mount environment variables securely (e.g., in CI/CD or secret management).\n- The Google/other OAuth flows may require redirect URIs configured in Raycast and provider consoles.\n- If the server cannot access Raycast services, verify network access and API key validity.\n- Use the provided example in claude_desktop_config.json to integrate the MCP with Claude Desktop workflows.\n- For NPX deployment, note the feature is marked as Coming Soon in the README; options may vary based on release.\n- Change the path /path/to/raycast-mcp/dist/index.js to the actual built entrypoint in your environment.