Songlinks › MCP server
Songlinks for Claude and other AI assistants
Ask an AI assistant who wrote a song, or which registrations belong to a songwriter, and it can ask Songlinks. The Songlinks MCP server gives Claude, and any other client that speaks the Model Context Protocol, the same answers as the site: the person behind a name or an IPI name number, with a link to their page.
- Add it
- The four tools
- What an answer holds, and its limits
- What a call sends us, and what we keep
- Support
Add it
The server’s address is:
https://songlinks.io/mcp
It needs no account and no sign-in. In Claude, open Settings › Connectors, choose Add custom connector and give it that address, or add Songlinks to Claude in one step. In Claude Code:
claude mcp add --transport http songlinks https://songlinks.io/mcp
Any other MCP client: add a remote server using the Streamable HTTP transport at the address above.
The four tools
Each one reads only. None of them changes anything, and none needs anything but the question.
find_songwriter— Find a songwriter by name- A full name, and optionally a song they wrote. Returns every person the name could be, each with a person ID, the names and IPI name numbers they are registered under, and how many works. The song says which of several writers with the same name wrote it.
get_songwriter— Get a songwriter by person ID- A Songlinks person ID, such as
SLP-Z3T8-G114-P. Returns the registrations joined into that person, the records kept apart as “possibly the same person”, and their first works. songwriter_by_ipi— Find a songwriter by IPI name number- One IPI name number, with or without its leading zeros. Returns the person, or persons, who hold it.
check_writers— Check a list of songwriters by IPI name number- Up to 50 IPI name numbers, such as the writers on a song or a registration file. For each: the person, the names they are registered under, and how many of their works sit under another spelling or number.
What an answer holds, and its limits
- Every person comes with their page,
https://songlinks.io/person/…, so the assistant can cite it and you can check it: the page shows what each join rests on. - At most 25 works per answer, with the total stated and the person’s page for the rest. Where a work’s registration carries an ISWC, the answer shows it.
- One question, one answer. Each tool starts from a name, an ID or a number you already have. There is no tool that lists or pages through songwriters or works.
- Shared capacity. Calls from every assistant share one budget. When it is used up, or Songlinks is busy, a tool answers “busy, retry in N s” rather than failing.
- Not a rights or royalty decision. Songlinks is in beta, and a grouping is a model’s judgement that no person has checked unless the page says so. Treat an answer as a lead to verify. Songlinks does not say who owns what share of a song.
How registrations are grouped into people, and how we check our answers: about Songlinks.
What a call sends us, and what we keep
A call sends Songlinks only what the assistant puts in it: a name and perhaps a song title, a person ID, or IPI name numbers. Songlinks never receives your conversation. We use what is sent to answer, and our logs record which tool was called, whether it answered, how many results, and how long it took — never the names, IDs or numbers themselves. The details, and how long anything is kept, are in the privacy notice.
Support
A tool that answers wrongly, or a grouping that is wrong, is what we want to hear about: email alex@songlinks.to. Songlinks is run by Kane Technology Group, LLC.