Rock Regeneration Gigs
Search upcoming gigs from the Rock Regeneration gig guide (southern England).
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0claude mcp add rock-regeneration-gigs -- docker run -i --rm ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0{
"mcpServers": {
"rock-regeneration-gigs": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"
]
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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-mcpTools
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-mcpExpected 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"Frequently asked questions
What is Rock Regeneration Gigs?
Search upcoming gigs from the Rock Regeneration gig guide (southern England).
How do I install Rock Regeneration Gigs?
It runs on your machine. In Claude Code: claude mcp add rock-regeneration-gigs -- docker run -i --rm ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Rock Regeneration Gigs need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Rock Regeneration Gigs open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains Rock Regeneration Gigs?
It is published by cuotos. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.