Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/swonvip/mcp-server-talk/docker-mcp-implementationgit clone --depth 1 https://github.com/SwonVIP/mcp-server-talkWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.01274 |
| Opus 5 | $0.00000 | $0.00637 |
| Sonnet 5 | $0.00000 | $0.00255 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
docker-mcp-implementation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker MCP Server Implementation Plan
Overview
This document outlines the implementation plan for converting the Python MCP server to use Docker, following the pattern established by the GitHub MCP Server.
Implementation Checklist
✅ Core Docker Files
- Dockerfile: Multi-stage build with Python 3.11 slim base
- .dockerignore: Exclude unnecessary files from build context
- docker-compose.yml: Container orchestration for development
- build.sh: Comprehensive build and management script
✅ Security Improvements
- Non-root user: Container runs as
mcpuser for security - Minimal base image: Using Python 3.11 slim to reduce attack surface
- No exposed ports: Uses stdio transport, no network exposure
- Clean dependencies: Only essential packages installed
✅ Code Modifications
- Removed hardcoded paths: Eliminated
/Users/sven.scheffel/recipe.txtdependency - Simplified add_numbers: Now returns just the calculation result
- Container-friendly: No file system dependencies outside container
✅ Configuration Files
- cursor-mcp-config-docker.json: Docker-based MCP client configuration
- Updated requirements.txt: Maintained existing FastMCP dependency
✅ Documentation
- README-Docker.md: Comprehensive Docker setup and usage guide
- Comparison table: Shows differences with GitHub MCP Server
- Troubleshooting guide: Common issues and solutions
- Multiple deployment options: Build script, Docker commands, Docker Compose
Architecture Comparison
| Component | GitHub MCP Server | Math Assistant MCP Server |
|---|---|---|
| Language | Go | Python |
| Base Image | golang:alpine | python:3.11-slim |
| Build Tool | Go build | pip install |
| Security | Non-root user | Non-root user (mcp) |
| Transport | stdio | stdio |
| Config | Environment variables | Direct configuration |
| Management | Build script | Build script + Docker Compose |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 196 lines · 0 tokens per session scan A 14c26976f060
docker-mcp-implementation is a cursor rule published in the GitHub repository SwonVIP/mcp-server-talk (0 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,274 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
backend
Backend development rules for TT Studio - AI model management backend.
devops-infrastructure
DevOps and infrastructure: Docker, Kubernetes, Terraform, CI/CD. Load when editing Dockerfiles, compose, k8s manifests, Terraform, or workflow YAML — not for application code.
hack
Hack v3 is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.
colima-docker-runtime
This workspace uses Colima for Docker; use compose-backed tests when Colima is running.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.