AllSolos MCP

Search and explore the AllSolos jazz solo catalog from any compatible Model Context Protocol (MCP) client.

The service provides read-only access to solos, soloists, tunes, albums, recordings, composers, and catalog insights. Solo and recording lookups can also return optional playback information and links to AllSolos.

Connect

Production endpoint: https://mcp.allsolos.com/mcp
Transport: Streamable HTTP
Authentication: None. The endpoint is public and does not require an AllSolos account, API key, or OAuth sign-in.

For clients that use an MCP server configuration, add:

{
  "mcpServers": {
    "allsolos": {
      "type": "streamable-http",
      "url": "https://mcp.allsolos.com/mcp"
    }
  }
}

Tools

Every tool is read-only: it retrieves catalog information and does not create, edit, or delete data or change account state. Optional IDs are numeric catalog IDs passed as strings. When an ID is omitted for an entity lookup, the service returns a random entry of that type.

search_allsolos

Searches across solos, soloists, tunes, albums, and recordings. Results include matching items with their group, display text, details, and AllSolos URL.

• Input: query (required string): names, tune titles, album titles, musicians, or other search terms.
• Output: data (array of search results), source_url (AllSolos search page).

{ "query": "Miles Davis So What" }

rank_solos

Ranks the full solo catalog by a measurable field and returns all tied winners. Catalog name filters must resolve to an exact name; ambiguous or missing names return choices or a clarification instead of ranking a guessed item. If exactly one winner has playback, playback_solo_id identifies it.

• Sort and order: sort is duration, choruses, tempo, or recording_year (default duration); order is asc or desc (default desc).
• Name filters: soloist, instrument, tune, album, recording (exact names).
• ID filters: soloist_id, instrument_id, tune_id, album_id, recording_id, segment_id.
• Musical filters: concert_key (concert pitch), local_key (written instrument key), key_mode (major or minor), meter_id, feel_id.
• Ranges: numeric duration_from/duration_to, choruses_from/choruses_to, tempo_from/tempo_to, and year_from/year_to.
• Playback filter: playback is any (default), available, or unavailable.
• Output: status (ok, ambiguous, not_found), winners, choices, clarification, sort, order, total, omitted_for_sort, and playback_solo_id. Each winner includes ID, solo name, soloist, tune, album, recording year, measured value, duration, playback availability, and URL.

{ "sort": "duration", "order": "desc", "soloist": "John Coltrane", "concert_key": "C" }

get_solo

Retrieves one solo and related catalog details. With a compatible client, playback metadata may render as an optional card; a link to the AllSolos page remains available.

• Input: optional id (numeric solo ID as a string); omit it for a random solo.
• Output: results, related links, optional YouTube/Spotify media, the source API data, and source_url for AllSolos. Media URLs may be null.

{ "id": "8" }

get_album, get_soloist, get_tune, get_recording, and get_composer

Each retrieves a catalog entity by numeric ID or returns a random entity when the ID is omitted. Each response contains the requested entity, an AllSolos url, and source API data. get_recording can also return playback metadata and a playback card in clients that support MCP Apps.

• Input: optional id (numeric catalog ID as a string).
• Output: entity field named for the tool (for example, album or soloist), url, and data. Recording results may also include results, media, source_url, and related recording details.

{ "id": "148" }

get_insight

Returns a catalog insight.

• Input: required topic: most-recorded-tunes, instruments-by-era, top-soloists, or top-solos.
• Output: data with the requested insight and source_url for the relevant AllSolos page.

{ "topic": "most-recorded-tunes" }

Errors and availability

Invalid inputs are rejected by the MCP tool schema. Exact-name ranking can return ambiguous or not_found, with a clarification or matching choices where available. If the catalog API is unavailable or returns an unsuccessful HTTP status, the MCP call returns an error; clients should report the failure and may retry later rather than presenting it as an empty result.

AllSolos has no published numeric request quota or rate limit for this endpoint. Requests remain subject to service availability and reasonable use.

Privacy and support

AllSolos receives the tool inputs needed for a request, such as search terms, catalog IDs, and filters, to retrieve catalog results. It does not receive the user's full conversation through these tools. The service does not require sign-in, an AllSolos account, or payment information. Operational logs for the MCP service and catalog API functions are retained for 30 days and may contain request details and technical information needed to operate, secure, and troubleshoot the service. AllSolos does not use these logs to build user profiles. The MCP client may handle prompts and results under its own privacy terms.

Read the AllSolos Privacy Policy or contact support@allsolos.com for questions. See also Terms of Use.