Rock Regeneration Gigs
Search upcoming gigs from the Rock Regeneration gig guide (southern England).
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
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
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent 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-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"
Questions fréquentes
Qu'est-ce que Rock Regeneration Gigs ?
Search upcoming gigs from the Rock Regeneration gig guide (southern England).
Comment installer Rock Regeneration Gigs ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add rock-regeneration-gigs -- docker run -i --rm ghcr.io/cuotos/rock-regeneration-gigs-mcp:2.0.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Rock Regeneration Gigs ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Rock Regeneration Gigs est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient Rock Regeneration Gigs ?
Il est publié par cuotos. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.