Skip to content
Gigmeister

Claude & ChatGPT (MCP)

Gigmeister connects to AI assistants through the Model Context Protocol (MCP). Once connected, the assistant reads and edits your band’s real data — the same songs, setlists, and calendar you see in the app — so you can prep a gig by describing what you want instead of tapping through screens. For an overview of what the connected assistant can do, see Claude & ChatGPT.

Tested end-to-end with Claude and ChatGPT. MCP is an open standard, so other assistants connect to the same server the same way — Gemini Spark and Microsoft Copilot Studio among them, with the caveats below.

Setup

Section titled “Setup”

One URL is all any client needs: https://gigmeister.app/api/mcp (also shown under Settings > Personal > MCP in the app, with a copy button). No API key, no configuration file — the assistant opens a browser window where you sign in with your Gigmeister account and pick the band to connect.

Claude

Section titled “Claude”
  1. In Claude (web or desktop), go to Settings > Connectors > Add custom connector
  2. Name it Gigmeister, paste the URL, and leave the OAuth fields empty — authentication is automatic

ChatGPT

Section titled “ChatGPT”
  1. In ChatGPT, go to Settings > Connectors and enable developer mode under Advanced
  2. Choose Create, name it Gigmeister, paste the URL, and pick OAuth as authentication
  3. Enable the connector in a conversation from the composer’s tools menu

Gemini

Section titled “Gemini”

The regular Gemini app does not take custom servers, but Gemini Spark does: add Gigmeister as a custom app by MCP URL in the Gemini web app, and it works in Spark on web and mobile. Gemini Enterprise connects through the Google Cloud console instead — that setup belongs to whoever runs your Workspace.

Microsoft Copilot

Section titled “Microsoft Copilot”

No consumer path — Copilot only reaches MCP servers through Copilot Studio custom connectors, an enterprise tool an admin provisions. If your workplace runs Copilot Studio, point the connector at the URL above; for personal use, Claude or ChatGPT is the way in.

The connection signs in as you. Every action follows your band role, so a Guest cannot edit what a Guest cannot edit in the app.

What You Can Ask

Section titled “What You Can Ask”

Building and reshaping a set:

  • “Build a 90-minute setlist for Saturday’s wedding — upbeat, nothing slower than 100 BPM”
  • “Make Sint-Margriete the same as Veerlepleintje”
  • “Reorder the second set so it builds energy through to the encore”
  • “Move ‘Layla’ to right before the ballads, then mark the last three as ENCORE”
  • “Give me the soundman link for Friday’s set”

Bringing your repertoire in:

  • “Here’s our set — add all of these songs to the library” (paste the list, up to 100 land in one go)
  • “Fill in the missing artists and durations for the songs you just added”

Working the catalog:

  • “Find songs in the key of G under 90 BPM”
  • “Transpose Kashmir down a whole step”
  • “Which songs have we played more than twice since January?”
  • “Find duplicate songs and merge them into the better copy”
  • “Which of our songs are in Dutch?”

Off-stage:

  • “What gigs are unconfirmed next month?”
  • “Draft a reply to the booking email from De Kreun”
  • “Which event does this booking thread belong to?”
  • “Show me what the band’s been practicing this month”

Multiple Bands

Section titled “Multiple Bands”

Every tool accepts an optional band_id to target a specific band you belong to for that call. It defaults to the connected band — use list_bands to find IDs.

Available Tools

Section titled “Available Tools”

Read-only tools, available to every role:

  • Songs: list_songs, search_songs, get_song, resolve_songs, list_songs_performed_since, analyze_catalog, find_duplicate_songs
  • Setlists: list_setlists, get_setlist, get_setlist_share_link
  • Groups: list_song_groups, get_song_group
  • Calendar: list_events, get_event, list_recurring_events
  • Practice: list_practice_sessions, get_practice_suggestions, get_active_practice_session
  • MIDI: list_midi_devices, list_midi_mappings, get_song_midi_settings
  • Band: get_band, get_band_members, list_bands, list_invitations
  • Inbox: list_mail_threads, get_mail_thread, search_mail, suggest_event_from_email
  • Rider Pack: get_rider_pack
  • Bin: list_bin
  • Help: search_docs (searches the Gigmeister help documentation)

Write tools, gated by your band role:

  • Songs: create_song, import_songs (up to 100 at once — paste a whole repertoire), update_song, delete_song, transpose_song, merge_songs, enrich_song, enrich_songs
  • Setlists: create_setlist, create_setlist_with_songs, duplicate_setlist, copy_setlist_contents, update_setlist, delete_setlist, add_song_to_setlist, bulk_add_songs_to_setlist, add_song_group_to_setlist, remove_song_from_setlist, move_song_in_setlist, reorder_setlist_songs, set_section_marker
  • Groups: create_song_group, update_song_group, delete_song_group
  • Calendar: create_gig, create_rehearsal, update_event, delete_event, update_attendance, set_member_attendance, confirm_all_attendance
  • Recurring: create_recurring_rehearsal, update_recurring_event, delete_recurring_event, skip_recurring_occurrence, unskip_recurring_occurrence
  • Practice: log_practice, start_practice_session, update_practice_session, end_practice_session
  • MIDI: create_midi_device, update_midi_device, delete_midi_device
  • Band: update_band
  • Inbox: update_mail_thread, add_mail_note, draft_mail_reply, send_mail_reply
  • Rider Pack: update_patchlist, set_rider_text, rotate_rider_pack_share_token, update_press_kit_file, reorder_press_kit_file, delete_press_kit_file, delete_rider_file
  • Bin: restore_from_bin, permanently_delete_from_bin, empty_bin

Building Your Own Integration

Section titled “Building Your Own Integration”

For scripts and services rather than an AI assistant, use the REST API with an API key.