Rock Regeneration Gigs
Search upcoming gigs from the Rock Regeneration gig guide (southern England).
Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
At most: only reads or looks up information.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
docker run -i --rm ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0
MCP client config
{
"mcpServers": {
"rock-regeneration-gigs": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"
]
}
}
}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.
| 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:
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
- The image is built and pushed to
ghcr.io/cuotos/rock-regeneration-gigs-mcp. - 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"
