What is Pinner MCP π: Immutable Pinning & Drift-Free AI Deployments?
Picture this: you're building an AI model that relies on third-party dependencies like Docker images or GitHub Actions workflows. But what if those dependencies suddenly change under your feet, breaking your deployment? Enter Pinner MCP, the vigilant gatekeeper that ensures your dependencies stay fixed to immutable cryptographic digests. Think of it as dependency time travelβyour code will always reference the exact artifact that existed when you pinned it, even if the world around it evolves. No more "it worked on my machine" drama.
How to use Pinner MCP π: Immutable Pinning & Drift-Free AI Deployments?
Let's get hands-on. To start, you'll need to summon Pinner MCP via Docker:
docker run -it --rm ghcr.io/safedep/pinner-mcp:latest
Next, configure Cursor by adding this magical incantation to your .cursor/mcp.json
:
{
"mcpServers": {
"pinner-mcp-stdio-server": {
"command": "docker",
"args": ["run", "--rm", "-i", "ghcr.io/safedep/pinner-mcp:latest"]
}
}
}
Now, when crafting your prompts with Composer, just whisper the names of dependencies you want to pin. For example:
Pin GitHub Actions to their commit hash
Pin container base images to digests
Updating pinned versions? Simply ask nicely:
Update pinned versions of container base images