Other clients
We are working on adding MCP support for other clients. If you are interested in using other clients, please contact us.
To try set up your client with Aurora MCP, use the MCP.JSON file within your client of choice.
Configure Aurora MCP
Warning:
Configuration Object Naming: Different MCP clients use different naming conventions for the server configuration object:
- Cursor, Windsurf: Uses
"mcpServers" - Claude Desktop, VS Code: Use
"servers"instead
Make sure to check your specific client’s documentation for the correct naming convention.
MCP configuration
{
"mcpServers": {
"aurora": {
"args": [
"@514labs/aurora-mcp@latest",
"--moose-read-tools",
"path/to/your/moose/project"
],
"command": "npx",
"env": {
"ANTHROPIC_API_KEY": "<your-anthropic-api-key>",
"MOOSE_PATH": "path/to/your/moose/installation",
"NODE_PATH": "path/to/your/node/installation",
"PYTHON_PATH": "path/to/your/python/installation"
}
}
}
}Adding other toolsets
For more information on available toolsets, see Aurora MCP toolsets. If the client you are using is a chat client, we recommend the following toolsets:
- Moose Read Tools: gives you chat access to your Moose project and the data within it (enabled by default)
- Remote ClickHouse Tools (read only): gives you chat access to your remote ClickHouse data
If it is an IDE type client, all toolsets are available.
Using the MCP
- Open the Claude Desktop application (note, you often have to reload the application after adding a new MCP)
- If you are using Moose tools, you will need to run your moose dev server
Common issues / troubleshooting
- 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 devin your Moose project directory. - The MCP is not running. Check your configuration and then restart the application.