# Rock Regeneration Gigs

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/cuotos/rock-regeneration-gigs-mcp  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/rock-regeneration-gigs

## Description
Search upcoming gigs from the Rock Regeneration gig guide (southern England).

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "rock-regeneration-gigs": {
    "command": "npx",
    "args": ["-y","rock-regeneration-gigs"]
  }
}
```

## Documentation & README

# rock-regeneration-gigs-mcp

An MCP server for searching upcoming gigs and live music events from the [Rock Regeneration gig guide](https://www.rock-regeneration.co.uk/gig-guide/), covering venues across southern England (Hampshire, Dorset, Wiltshire, Isle of Wight, etc).

## Usage

Add to your Claude config:

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

Or with the Claude CLI:

```bash
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.

| Parameter   | Type   | Description                                      |
|-------------|--------|--------------------------------------------------|
| `location`  | string | Town or city (expands to nearby towns)           |
| `artist`    | string | Artist or band name (partial, case-insensitive)  |
| `venue`     | string | Venue name (partial, case-insensitive)           |
| `from_date` | string | Start date filter — `YYYY-MM-DD`                 |
| `to_date`   | string | End date filter — `YYYY-MM-DD`                   |

## Testing

Build the image locally:

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

Test it responds correctly:

```bash
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:

```json
{"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:

```bash
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](https://registry.modelcontextprotocol.io) 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:

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