Search upcoming gigs from the Rock Regeneration gig guide (southern England).
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).
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
search_gigsSearch 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 |
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":"..."}}}
Pushing a version tag does both halves of a release:
git tag v1.0.0
git push origin v1.0.0
ghcr.io/cuotos/rock-regeneration-gigs-mcp.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"
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
docker run -i --rm ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-cuotos-rock-regeneration-gigs-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0dockerRock Regeneration Gigs works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.