Connect an AI assistant

You can let an AI assistant — Claude Code, or any other assistant that supports MCP connections — look at your band’s calendar and network, and help with the busywork: “who’s on our fan list in Philly?”, “draft an invite for Friday’s show to everyone who came last time.”

The assistant connects with a key you create in muze. A key belongs to one band. If you book for several bands, make a key in each one.

What an assistant can do

With any key, it can look up:

• your shows and bookings, including who’s on each bill
• your venues, acts, and people (including your fan list)
• venues in the muze directory you could add
• invites for a show, and who came

With a Read & write key, it can also:

• add people and fans, and edit them
• write invite drafts for a confirmed show, and edit drafts
• mark an invite as sent (or take that back)
• record who came to a show, including walk-ups

An assistant never sends anything. Invites stay drafts until someone in the band sends them from their own phone or Instagram and marks them sent. It can’t delete or archive anything, change your band’s settings, or reach any other band.

Create a key

Only a band’s owner can manage keys.

1. Open Settings → Integrations.
2. Under MCP keys, click Create key.
3. Give it a Name you’ll recognize later, like “Claude Code on my laptop”.
4. Choose its Access:
   • Read — the assistant can look, but not change anything.
   • Read & write — it can also make the changes listed above.
5. Optionally pick an Expires date. The key works through the end of that day, then stops. Leave it blank for a key that doesn’t expire.
6. Click Create key.

muze shows the key once. Click Copy and keep it somewhere safe, like your password manager. muze won’t show it again — if you lose it, revoke it and make a new one.

Treat the key like a password: anyone who has it can do whatever its access level allows, in this band.

Paste it into your assistant

Your assistant needs two things: muze’s MCP address and your key. The address is the one you open muze at, with /mcp on the end:

https://app.muze.krondor.org/mcp

Claude Code

Run this in a terminal, with your key in place of YOUR_KEY:

claude mcp add --transport http muze https://app.muze.krondor.org/mcp \
  --header "Authorization: Bearer YOUR_KEY"

Then start Claude Code and ask it something like “what’s on our calendar next month?”. Type /mcp inside Claude Code to check that muze shows as connected.

Other assistants

Most assistants that support MCP take a settings snippet like this one. Look for “MCP servers” in your assistant’s settings and add:

{
  "mcpServers": {
    "muze": {
      "type": "http",
      "url": "https://app.muze.krondor.org/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

The key always goes in the Authorization header, as Bearer followed by a space and the key. muze refuses a key pasted into the address itself.

If you manage several bands, add one connection per band, each with its own key and its own name (for example muze-glass-atlas).

Keep track of your keys

Settings → Integrations lists every key for the band: its name, the first few characters of the key (so you can tell keys apart without revealing them), its access, who created it and when, when it expires, when it was last used, and its status — Active, Expired, or Revoked.

A key keeps working if the person who made it leaves the band or stops being an owner. If you no longer trust a key, revoke it.

Revoke a key

1. Open Settings → Integrations.
2. Find the key and click Revoke.
3. Confirm with Revoke key.

Anything using that key loses access on its very next request. Revoking can’t be undone — make a new key if you need to reconnect. Revoked keys stay in the list so you can see what existed.

Next: The booking playbook.