Skip to main content
Glama

tarana-mcp

A read-only Model Context Protocol server that lets an AI assistant answer questions about my band's data - songs, setlists and shows - straight from the Supabase project behind the Tarana Setlist Manager app.

Ask things like:

  • "What songs do we have in G that are over 120 BPM?"

  • "Show me the setlist for Friday's gig, in order."

  • "How many shows are coming up?"

Why this exists

The setlist manager is a Next.js + Supabase app with row-level security on every table. This server exposes that same data to agent tooling over MCP, with the same RLS guardrails: it only ever runs SELECTs, and it can only read what the credentials you give it are allowed to see.

Related MCP server: Supabase MCP Server

Tools

Tool

What it does

list_songs

List repertoire, filter by search text, key, BPM range

get_song

One song with chord chart and notes

list_setlists

Recent setlists

get_setlist

A setlist with its songs in performance order

list_shows

Upcoming/past shows, filter by booking status

get_show

One show plus its setlist

suggest_songs

Set-builder helper: songs by key/BPM

band_stats

Counts: songs, setlists, total and upcoming shows

Setup

npm install
cp .env.example .env   # fill in SUPABASE_URL and SUPABASE_ANON_KEY
npm run build

Claude Code

claude mcp add tarana -- node /path/to/tarana-mcp/dist/index.js

Claude Desktop / any MCP client

{
  "mcpServers": {
    "tarana": {
      "command": "node",
      "args": ["/path/to/tarana-mcp/dist/index.js"],
      "env": {
        "SUPABASE_URL": "https://your-project-ref.supabase.co",
        "SUPABASE_ANON_KEY": "your-anon-key"
      }
    }
  }
}

If your RLS policies scope rows to auth.uid(), also set SUPABASE_ACCESS_TOKEN to a signed-in user's session token. Without it the server reads whatever the anon role may see - which is the correct behaviour for a public deployment.

Safety

  • Read-only: not one insert, update, delete or RPC in the code.

  • No secrets in the repo: credentials come from .env or the client config.

  • RLS is the enforcement layer; the anon key is safe to use because your policies already decide what it can read.

Stack

TypeScript, @modelcontextprotocol/sdk (stdio transport), @supabase/supabase-js, zod.

Available Tools

8 tools
band_statsBand statsA

Quick overview: total songs, setlists, shows, and how many shows are coming up.

Inputs: no named parameters.

get_setlistGet a setlistA

Get one setlist by id with its songs in performance order, grouped by section when sections are used.

Inputs: setlist_id (required).

get_showGet a showA

Get one show by id, plus its setlist when one exists.

Inputs: show_id (required).

get_songGet a songB

Get one song by id, including its chord chart and rehearsal notes.

Inputs: song_id (required).

list_setlistsList setlistsC

List setlists, newest first.

Inputs: limit.

list_showsList showsB

List shows (gigs). Filter upcoming/past and by booking status (e.g. Enquiry, Confirmed, Advance Received, Completed).

Inputs: when, limit, booking_status.

list_songsList songsB

List songs in the band's repertoire, optionally filtered by a title/artist search, musical key, or minimum/maximum BPM.

Inputs: limit, search, bpm_max, bpm_min, +1 more.

suggest_songsSuggest songs for a setC

Suggest songs for building a set, filtered by key and/or BPM range. Useful for 'give me upbeat songs in G' style requests.

Inputs: limit, bpm_max, bpm_min, song_key.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools have clear resource/action boundaries (list/get for songs, setlists, and shows; band_stats is distinct). However, suggest_songs overlaps substantially with list_songs, since both filter songs by key and BPM range, and the distinction is only loosely clarified as 'for building a set.'

    Naming Consistency4/5

    The set mostly follows a consistent snake_case verb_noun pattern: list_songs, get_song, list_setlists, get_setlist, list_shows, get_show, and suggest_songs. band_stats is the one deviation, using a noun phrase with no verb, but it is still readable and predictable.

    Tool Count5/5

    Eight tools is well-scoped for a band repertoire/setlist/show assistant. Each tool covers a clear read-oriented operation, and there is no excessive surface area.

    Completeness3/5

    The read side is solid: songs, setlists, and shows all have list/get coverage, plus suggestions and stats. However, the surface has no create/update/delete operations for songs, setlists, or shows, and no way to edit setlists or booking status, which are notable gaps for a band management domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with Supabase databases through standardized CRUD operations including querying, inserting, updating, and deleting records with support for filtering, pagination, and column selection.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Connects to a Gym Tracker Supabase database to provide LLMs with access to personal workout history, routines, and training progress. It enables users to analyze fitness performance, track personal records, and receive personalized coaching advice through natural language.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search and retrieve read-only ISHARI shalawat content from Supabase, including verse translations, full chapters, audio recitations, reciters, and per-user bookmarks through MCP tools.
      -