As always, to get the latest:

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

Friday, 16th May 2025

Highlights:

  • Aurora users can now leverage DuckDB for local data wrangling.

Moose + Aurora

Quality of life and bug fixes:

  • Flexible JSON ingest. Our agents were confused by needing to specify whether ingested data was a JSON object or an array of JSON objects. Now by default both work.

Aurora MCP

[External] DuckDB MCP

You can now bring DuckDB’s MCP tool into a Moose Project and manage that MCP through the Aurora CLI! Try aurora config tools and enable external-duck-db-mcp. Docs. You’ll need to configure the MCP with your duckdb path—either after selectign the tool-set through aurora config tools, or by editing the MCP.json file directly.

String DuckDB tool calls with Aurora tool calls to manipulate local files for ingestion. Try our Aurora tools for creating a DuckDB database from your local flat files.

Future of the feature:

  • Remote Data: We’re working on bringing remote data into Moose management with this MCP toolset

Data Collection

Aurora is in research preview, to help us improve our product, we’ve added data collection to our MCP tools. Ready-to-go templates default to comprehensive data collection (we figure that these templates are least likely to have sensitive information), and standard templates default to standard data collection. You can change your data collection preferences whenever you want (just by editing your project’s aurora.config.toml file. Docs.

Aurora CLI

Quality of life and bug fixes:

  • LLM Docs. Want docs for your LLMs that work with Moose projects? Here.
  • Read only tools. We’ve had requests for a read-only toolset, especially for people using chat based MCP clients. We’ve split standard tools into: read-only and egress-tools. Docs.
  • Sorting Projects. Projects in the CLI are now sorted (hopefully y’all have enough Aurora projects that this is useful)! Affects aurora config tools and structure of ~/.aurora/config.toml. Docs. Deleted projects will now be cleaned from ~/.aurora/config.toml and from whenever the CLI prints lists of projects.
  • 🐛Read tools now only read. clickhouse read tool was doing a little more than read, especially when used by Claude. Tool has been tightened up, and if you want extra certainty, create a read-only user (see snippet below).
CREATE USER username IDENTIFIED BY 'password' SETTINGS PROFILE 'readonly'
GRANT SHOW TABLES, SELECT ON db+name.* TO username

In Progress

Let us know if these features are interesting to you, we are always looking for beta users, design partners, and general feedback!

  • Google Docs MCP integration. Get data from Google Docs / Sheets for use as context, or as a source!
  • First Party Chat. Chat with your data from our hosting platform, Boreal.

Sneak Peek: First Party Chat

Actively seeking feedback on this one!

A user can start a chat anywhere in Boreal—in a project, on a table view, wherever they might be. Where they start the chat informs:

  1. the context that is available to the chat
  2. the actions that the chat window suggests that the user takes.

Starting a new chat

Here’s an example of autocomplete—the chat suggests relevant tables and files to use as context. You can accept the suggestion, select specific context to add with “tab”. You can add other context with ”@”.

Autocomplete

Here’s an example of chat with tool-calls.

Chat

The user can create persistent artifacts in chat (not static, they receive data from APIs created by the MCP tools called in the chat)

Artifacts

The user can then deploy and share those artifacts.