> For the complete documentation index, see [llms.txt](https://helpdesk.rhapsody.la/updates/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.rhapsody.la/updates/readme.md).

# Rhapsody 9.0.0 (June 15th 2026)

Rhapsody 9.0 is our biggest release yet. It introduces the **Rhapsody Library**, a complete music-library and librarian toolkit, brings **AI access** to your data through MCP, adds a **global search** across everything, and ships our first additional language: **French**.

{% hint style="info" %}
Some features in this release are available on request. If you don’t see them yet, contact your Rhapsody admin or support to enable them.
{% endhint %}

### 📚 The Library

A brand-new module to manage your physical and digital music library — built for librarians, and connected to the Projects you already run in Rhapsody.

* **Catalog your pieces:** title, composer and contributors, movements, durations, and full instrumentation — all in one place.
* **Library entries:** track editions, catalog numbers, publishers, and the materials (scores & parts) you actually own.
* **Locations:** organize your physical library by **institution, room, shelf, and bin** so anyone can find a part in seconds.
* **Markings & Bowings:** build **marking sets** and **marking sheets**, and apply bowings and markings to a piece.
* **Usage history:** see every Project that has used a given library entry.
* **Import from Daniels:** look up an orchestral work and import its instrumentation, movements, durations, and credits directly from **Daniels’ Orchestral Music**.
* **Instrumentation shorthand:** type a shorthand string and Rhapsody expands it into the full instrumentation for you.
* **Project Librarian:** a dedicated **Librarian** view on every Project to hand out materials and manage markings for that program.

### 🤖 AI access & MCP

* **API keys:** generate personal access tokens right from your account.
* **Connect Rhapsody to AI assistants:** each account now has an **MCP** (Model Context Protocol) endpoint, so you can use your Rhapsody data with **Claude** and other AI tools — ask questions, draft communications, and pull reports in natural language.

### 🔎 Global search

* A new **advanced search** spanning all your data — musicians, projects, pieces, venues, and more — reachable from anywhere with a keyboard shortcut.

### 🌍 Languages

* Rhapsody is now available in **French**, in addition to English.
* Switch languages anytime — your choice is remembered on your device.

### Projects

* **Project v3 can now have Pieces.** Building on the Project v3 introduced in 8.0, you’re no longer limited to piece-less projects.

### Booklets

* **Dynamic merge tags:** Booklets now support a large set of placeholders that fill in automatically — Season info and schedules, Project details, rosters, detailed programs, credits, notes, contacts, carpool, and the event timeline.
* **Season booklets:** generate a Season overview alongside your Project booklets.

### Musicians

* **Event timeline:** review a musician’s event history at a glance, with an export.

### Misc

* Cleaner **piece name formatting** and consistent **duration** display across the app.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.rhapsody.la/updates/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.