Getting Started

Terminal

bash -i <(curl -fsSL https://fiveonefour.com/install.sh) aurora,moose

Create a new project with Cursor MCP preconfigured:

Terminal

aurora init <project-name> <template-name> --mcp cursor-project

If you want to use this as a global Cursor MCP, use cursor-global instead of cursor-project.

For other options, see Aurora CLI docs.

For more information on available toolsets, see Aurora MCP toolsets. All toolsets are available for Cursor.

Open Cursor
You will see a popup saying that an MCP is detected, and can be enabled. Our experience is that this is not always reliable, and the MCP is more stably launched if you go to cursor > settings > cursor settings > tools and integrations and enable the MCP there.
If you are using Moose tools, you will need to run your moose dev server with moose dev.

Every time you add an MCP or change its configuration, you will need to reload the MCP. You can do this by going to cursor > settings > cursor settings > tools and integrations and toggling the MCP off and on. If this doesn’t work, you can also restart the Cursor application.
If you have configured the MCP globally, and want to change the Moose Project that the Aurora MCP is referring to, manually edit the MCP.JSON file or run aurora config focus and select a new project.

The MCP is running, but you aren’t able to get your data? Look at the tool call response, it will tell you if your Moose dev server is running. If it is not, run moose dev in your Moose project directory.
The MCP is not running. Check your configuration and then restart the application.