mcpField
R
Rock Regeneration Gigs

Rock Regeneration Gigs

Local
github.com/cuotosGames & Entertainment0Updated 5w ago
Repository

About Rock Regeneration Gigs

Rock Regeneration Gigs is an MCP server for finding upcoming live music events in the Rock Regeneration gig guide across southern England. Its search filters cover location, artist, venue, and date range.

Key features

  1. 01Search upcoming gigs
  2. 02Filter by town or city
  3. 03Match artist or band names
  4. 04Filter by venue and dates

Use cases

  1. 01Find gigs near a town
  2. 02Look up an artist’s upcoming shows
  3. 03Browse events at a venue
  4. 04Search gigs within a date range

MCP support

It exposes the gig guide search as the `search_gigs` tool for MCP clients, with optional location, artist, venue, and date filters.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cuotos-rock-regeneration-gigs": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"
      ]
    }
  }
}
Run commanddocker run -i --rm ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

rock-regeneration-gigs-mcp

An MCP server for searching upcoming gigs and live music events from the Rock Regeneration gig guide, covering venues across southern England (Hampshire, Dorset, Wiltshire, Isle of Wight, etc).

Usage

Add to your Claude config:

{
  "mcpServers": {
    "gigs": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "ghcr.io/cuotos/rock-regeneration-gigs-mcp"]
    }
  }
}

Or with the Claude CLI:

claude mcp add --transport stdio gigs -- docker run --rm -i ghcr.io/cuotos/rock-regeneration-gigs-mcp

Tools

search_gigs

Search for upcoming gigs. All filters are optional — omit to return everything.

ParameterTypeDescription
locationstringTown or city (expands to nearby towns)
artiststringArtist or band name (partial, case-insensitive)
venuestringVenue name (partial, case-insensitive)
from_datestringStart date filter — YYYY-MM-DD
to_datestringEnd date filter — YYYY-MM-DD

Testing

Build the image locally:

docker build -t rock-regeneration-gigs-mcp .

Test it responds correctly:

echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0"}}}' \
  | docker run --rm -i rock-regeneration-gigs-mcp

Expected output:

{"jsonrpc":"2.0","id":1,"result":{"capabilities":{"tools":{}},"protocolVersion":"2024-11-05","serverInfo":{"name":"rock-regeneration-gigs-mcp","version":"..."}}}

Publishing

Pushing a version tag does both halves of a release:

git tag v1.0.0
git push origin v1.0.0
  1. The image is built and pushed to ghcr.io/cuotos/rock-regeneration-gigs-mcp.
  2. The server is published to the MCP Registry as io.github.cuotos/rock-regeneration-gigs-mcp, using GitHub OIDC — no secrets needed.

server.json keeps a placeholder 0.0.0 version in git; CI rewrites it, and the image tag, from the git tag at publish time.

The registry verifies ownership by pulling the image and reading its io.modelcontextprotocol.server.name label, so the GHCR package must be public. It is private on first push — make it public once, under the package settings on GitHub.

Check the published entry with:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.cuotos/rock-regeneration-gigs-mcp"

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.