Blog

Read the latest news from the Chatmu blog.

Back to blog
October 26, 2026

MLC MCP Server: Find Unclaimed Mechanical Royalties with AI

  • Name
    Chema Rodriguez
    #Royalties
    #MCP
    #The MLC
    #Publishing
    #Songwriters
MLC MCP Server: Find Unclaimed Mechanical Royalties with AI

An MLC MCP server lets an AI agent check your songs against The MLC's public database, so you can see which of your works are unregistered or missing your writer IPI, and why their US streaming mechanical royalties are not reaching you. Chatmu's MLC connector does the audit across your whole catalog, then prepares the registration drafts and the bulk files you upload to The MLC yourself. When I ran it on my own catalog, 62 of 135 works were not registered.

I'm Chema Rodriguez. I produce, I engineer, and I run a label with around 500 tracks and about ten music YouTube channels. I built this connector because checking that catalog by hand, one ISRC at a time in a portal, was never going to happen. Here is how The MLC works, why money goes unmatched, and the exact workflow I use.

What is The MLC and why do royalties go unmatched?

The Mechanical Licensing Collective (The MLC) was created by the US Music Modernization Act. Since January 2021 it administers the blanket license for digital audio services in the United States: it collects the mechanical royalties that streaming and download services owe for the composition (the song, not the master) and pays them to songwriters and publishers.

This is where many independent writers lose money. Your performance rights organization (ASCAP, BMI, SACM, SGAE and so on) collects performance royalties. It does not collect US streaming mechanicals on your behalf. Your distributor pays you for the master recording. If nobody has registered your works with The MLC and linked them to your recordings, those mechanicals sit there as unmatched.

A royalty becomes unmatched when a streaming service reports a recording (identified by its ISRC) and The MLC cannot connect it to a registered musical work with known owners. Typical causes:

  • The work was never registered at all.
  • The work exists but has no writer IPI, so the money cannot be routed to a person.
  • The recording's ISRC is not linked to the work's MLC Song Code.
  • Shares are wrong or duplicate writer profiles split the data.

The MLC holds unmatched royalties and keeps trying to match them. It also runs the Distributor Unmatched Recordings Portal (DURP), which lets independent distributors see which of their releases have unmatched royalties so they can push their artists to register.

Why this matters before 2027

Unclaimed money does not wait forever. According to The MLC's market share page, it intends to begin market share distributions in April 2027, starting with the remaining royalties from January 2021, and it recommends registering missing works, claiming unclaimed shares and submitting match suggestions well before its February 2027 database snapshot. Money that is still unclaimed at that point gets paid out by market share, which mostly means to whoever already has the best data. Connecting with The MLC is free, so there is no reason to leave your share on the table.

What the MLC MCP server in Chatmu does

Chatmu is an AI agent for the music industry with its own catalog of music-industry MCP connectors. The MLC is one of them, built by Chatmu on top of The MLC's public data. You can use it inside the Chatmu agent at chatmu.io or on WhatsApp, or plug the connector into any MCP client. Full list of connectors at chatmu.io/mcp.

What you needToolWhat it returns
MLC lookup by ISRCmlc_lookup_by_isrc, mlc_search_recordingsThe recording, its MLC Song Code and the full work: writers with IPIs, publishers with collection shares, AKAs, ISWC
Find a work by title and writermlc_search_works, mlc_get_work, mlc_get_works_batchMatching works with ISWC and Song Code, and the complete ownership tree
Writer catalogmlc_get_writer_catalogWorks registered to a writer (by last name and title, optionally IPI)
Who gets paidmlc_resolve_ownershipA royalty tree with every writer and publisher and their shares
Catalog auditmlc_audit_catalog, mlc_cross_reference_catalogEach ISRC labelled registered with IPI, registered without IPI (at risk), or not registered
Registration draftsmlc_build_registration_draft, mlc_validate_registration, Registration WizardA draft pre-filled with existing MLC data, checked against MLC rules with per-field fixes
Bulk filesmlc_export_bulk_excel, mlc_export_bulk_match_csvThe Bulk Work Registration .xlsx and the Bulk Match CSV (ISRC to Song Code)
Follow-upmlc_parse_ack_file, mlc_generate_correction_ticketACK results mapped back to your works; ready-to-paste support tickets for merges, missing IPIs, wrong shares or duplicates

One thing it does not do: it does not register anything on The MLC by itself. It reads public MLC data and produces files and texts. You review them and you submit them through your MLC account. That is deliberate. Registrations carry legal ownership claims, so a human signs off.

Step by step: how to register songs with The MLC using AI

1. Ask for the audit

In Chatmu, click the “Publishing audit (MLC)” button or type something like:

“Audit my catalog against The MLC to find songs where I'm losing mechanical royalties. Pull my full catalog with ISRCs, ask me for my songwriter IPI, cross-reference each ISRC against The MLC, and give me a list of songs not linked to my IPI. Deliver it as a PDF with steps to register the missing ones.”

The agent pulls your releases from Chatmu (including what you distributed with us), asks for your IPI if it doesn't have it, and runs every ISRC through The MLC.

2. Read the gaps

You get three buckets: works that are clean, works registered without your IPI (money at risk), and recordings with no work registered at all. My own run: 135 works checked, 62 not registered. The report comes as a PDF you can send to your team or your publisher.

3. Build and validate the drafts

For each gap, the agent builds a registration draft. If the work already exists in The MLC, the draft is pre-filled with the Song Code, writer IPIs, publishers, shares and ISWC, so you only fill what's missing. Then it validates: required fields, IPI format, 12-character ISRCs, shares that don't exceed 100%, writer role codes, at least one composer or author. Errors come back per field with a suggested fix. If you prefer a form, the Registration Wizard opens inside the chat and walks you through the same steps.

4. Export the bulk file

Validated works go into an .xlsx that matches The MLC's Bulk Work Registration template (up to 300 rows per file, with one row per writer, publisher and recording). For recordings that exist but aren't linked to a work, the agent can build a Bulk Match CSV that pairs each ISRC with its MLC Song Code.

5. You submit

You upload the Excel in your MLC Member Hub under Works Registration, Bulk Registration, and you send the match file through the channel The MLC specifies. When The MLC replies with ACK files, paste them back into the chat and the agent maps each status (accepted, rejected, accepted with changes, conflict) to your works. If something needs The MLC's staff, such as merging duplicate writer profiles or fixing shares, it drafts the support ticket for you to send.

A tip from experience: turn this into a scheduled task, for example a quarterly re-run of the audit on new releases delivered to your WhatsApp. New songs get caught before their royalties pile up.

Who is it for?

  • Self-published songwriters who own their publishing and have never touched The MLC. If you have more than 30 released songs, odds are some are unmatched.
  • Small publishers who need to register dozens or hundreds of works without retyping each one in a portal.
  • Labels and distributors who want to check that their catalog's recordings are linked to works, and help their writers claim what's theirs.
  • Managers and admins who need a clear, shareable report of what's missing.

In Team Mode, this lands with the Publishing & Legal or Royalties & Admin specialist, who keeps memory of your writers, IPIs and past submissions. For the bigger picture on music MCPs, read the complete guide to MCP in the music industry.

Is this an official MLC tool?

No. The MLC connector is built by Chatmu. Chatmu is not affiliated with, endorsed by or operated by The Mechanical Licensing Collective. The connector uses The MLC's public data and produces files in The MLC's published formats. All registrations, claims and payments happen in your own MLC account, under The MLC's terms.

FAQ

What is an MLC MCP server?

It is a Model Context Protocol server that gives an AI agent tools to query The MLC's public data: works, recordings, writers and ownership. Chatmu's version also builds registration drafts and bulk files.

Does Chatmu register my songs with The MLC automatically?

No. Chatmu prepares and validates the drafts and the bulk files. You review them and submit them in your MLC account.

Can I do an MLC lookup by ISRC?

Yes. Give the agent an ISRC and it returns the matched work, the MLC Song Code, writers with IPIs, publishers with shares, and the ISWC, or tells you nothing is linked.

My PRO already pays me. Do I still need The MLC?

Yes, if your music streams in the US. PROs collect performance royalties; US streaming mechanicals are paid by The MLC to registered works.

How much does it cost?

There is a free plan to try the audit. ACK file parsing is part of the Business plan; see pricing.

AI for the industry. Humans for the music.


Try Chatmu → | See pricing →

]]>