Skip to content
emely. docs

Overview

emely exposes two machine interfaces on top of its catalogue:

  • The MCP server at https://mcp.emely.io/mcp lets MCP clients such as Claude and ChatGPT read and maintain emely data as tools.
  • The REST API at https://api.emely.io exposes the same operations over HTTP. The MCP server is itself a client of the API, and the API is the one place where the access rules are enforced.

Version 1 covers one use case: the collecting-society catalogue, for emely operators. A collecting society is an organisation such as GEMA, AKM or SUISA that collects royalties on behalf of rightsholders. The catalogue records each society’s roles, the rights it collects, its detail rights and its links to other societies.

Both interfaces require an emely account and an OAuth 2.1 sign-in. See Authentication.

Personal data is never reachable through either interface. See Data and privacy.