Skip to content

electron.dance

by Ric-Lavers · remote · no sign-in to list tools · v0.1.0 · published by GitHub user Ric-Lavers

electron.dance MCP server: upcoming gigs, community links, RSVP, and Spotify top tracks.

Changes · 1

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http electron-dance https://electron.dance/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • rsvp_to_gigSet attendance status for a gig (going, maybe, or none to clear it), on behalf of the site's configured default user.No findings

    Why it is in this group

    • The description's first verb is "set": a word for a change.
    Description, as the server wrote it
    Set attendance status for a gig (going, maybe, or none to clear it), on behalf of the site's configured default user. Requires a bearer token.
Only reads 3Claude Code: allow
  • get_top_tracksGet electron.dance's current Spotify top tracks (short term).No findings

    Why it is in this group

    • The name "get_top_tracks" says "get": a word for reading.
    Description, as the server wrote it
    Get electron.dance's current Spotify top tracks (short term). Requires a bearer token.
  • list_upcoming_gigsList upcoming electron.dance gigs, each with its current going/maybe attendance.No findings

    Why it is in this group

    • The name "list_upcoming_gigs" says "list": a word for reading.
    Description, as the server wrote it
    List upcoming electron.dance gigs, each with its current going/maybe attendance. Use this for 'what's on tonight/this week/this weekend' style questions instead of scraping the website — results are sorted soonest-first, so filter/take the first entries for 'tonight'. Open to anyone.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http electron-dance https://electron.dance/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__electron-dance__list_upcoming_gigs",
      "mcp__electron-dance__get_top_tracks",
      "mcp__electron-dance__get_site_links"
    ],
    "ask": [
      "mcp__electron-dance__rsvp_to_gig"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as electron-dance. Review it before you use it.