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/gerred/mcpmc/cursorrulesgit clone --depth 1 https://github.com/gerred/mcpmcWhat 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.02356 | $0.02356 |
| Opus 5 | $0.01178 | $0.01178 |
| Sonnet 5 | $0.00471 | $0.00471 |
| Haiku 4.5 | $0.00236 | $0.00236 |
Grade A, and why
cursorrules 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 2d ago.
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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.cursorrules
⚠️ IMPORTANT: JSON-RPC Warning
If you find yourself implementing JSON-RPC directly (e.g., writing JSON messages, handling protocol-level details, or dealing with stdio), STOP! You are going in the wrong direction. The MCP framework handles all protocol details. Your job is to:
- Implement the actual Minecraft/Mineflayer functionality
- Use the provided bot methods and APIs
- Let the framework handle all communication
Never:
- Write JSON-RPC messages directly
- Handle stdio yourself
- Implement protocol-level error codes
- Create custom notification systems
Overview
This project uses the Model Context Protocol (MCP) to bridge interactions between a Minecraft bot (powered by Mineflayer) and an LLM-based client.
The essential flow is:
- The server starts up ("MinecraftServer") and connects to a Minecraft server automatically (via the Mineflayer bot).
- The MCP server is exposed through standard JSON-RPC over stdio.
- MCP "tools" correspond to actionable commands in Minecraft (e.g., "dig_area", "navigate_to", etc.).
- MCP "resources" correspond to read-only data from Minecraft (e.g., "minecraft://inventory").
When an MCP client issues requests, the server routes these to either:
• The "toolHandler" (for effectful actions such as "dig_block")
• The "resourceHandler" (for returning game state like position, health, etc.)
MCP Types and Imports
When working with MCP types:
- Import types from the correct SDK paths:
- Transport: "@modelcontextprotocol/sdk/shared/transport.js"
- JSONRPCMessage and other core types: "@modelcontextprotocol/sdk/types.js"
- Always check for optional fields using type guards (e.g., 'id' in message)
- Follow existing implementations in example servers when unsure
- Never modify working type imports - MCP has specific paths that must be used
Progress Callbacks
For long-running operations like navigation and digging:
- Use progress callbacks to report status to MCP clients
- Include a progressToken in _meta for tracking
- Send notifications via "tool/progress" with:
- token: unique identifier
- progress: 0-100 percentage
- status: "in_progress" or "complete"
- message: human-readable progress
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.
- 2d ago First seen · 276 lines · 2,356 tokens per session scan A 371bf8aefe1a
cursorrules is a cursor rule published in the GitHub repository gerred/mcpmc (40 stars, last pushed 1y ago), licensed MIT. It adds 2,356 tokens to every session, about $0.0118 per session on Opus 5. 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.