510-mcp-servers

510-mcp-servers is a cursor rule for Cursor from d-padmanabhan/agent-engineering-handbook. It costs 17 tokens per session (4,511 once invoked), scanned C, original, MIT.

A set of rules for building MCP servers, which let AI applications connect to external tools and data through a shared standard.

In plain words
What is it for?
It guides MCP tool documentation, capability descriptions, authentication, deployments, and integrations with AI clients.
Why use it?
It helps make tools understandable to AI agents and supports consistent descriptions, safe use, and reliable long-running operations.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions Claude Code.

Good fit It guides MCP tool documentation, capability descriptions, authentication, deployments, and integrations with AI clients.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers
Install

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.

Clone the repo
git clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbook

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for 510-mcp-servers

README.md
[![agentmods](https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers/github.svg)](https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers)
Your own site
<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for 510-mcp-servers

Your own site · 80×15
<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/510-mcp-servers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,511 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.04511
Opus 5 $0.00009 $0.02256
Sonnet 5 $0.00003 $0.00902
Haiku 4.5 $0.00002 $0.00451

Measured 6d ago against content hash 13fae2e5a397, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade C, and why

510-mcp-servers scanned grade C with 1 finding 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 6d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

if any(dangerous in command for dangerous in ['rm -rf', '> /dev/', '|', ';']):
rules/510-mcp-servers.mdc · 702 lines

How it starts

The opening of the file, as written. The whole thing — 702 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP Server Engineering Ruleset

Goal: Build MCP servers with rich, AI-agent-friendly documentation that enables effective tool selection and usage.

About MCP

The Model Context Protocol (MCP) is a vendor-neutral, open standard managed by the Linux Foundation's Agentic AI Foundation. MCP enables consistent AI agent integration across platforms (Claude Code, Cursor, GitHub Copilot, and others), solving the n×m integration problem where every AI client had to integrate separately with every tool.

Key Capabilities:

  • Multi-vendor: GitHub, Microsoft, OpenAI, Anthropic, community-supported
  • Enterprise-ready: OAuth for remote servers, no proprietary tokens
  • Long-running tasks: Support for builds, deployments, multi-minute operations
  • Discoverable: MCP Registry for governance and discoverability
  • Production-grade: Industry-standard maturity (like Kubernetes, GraphQL)

Core Principle

Exception to lean comment rules: MCP tools require detailed docstrings because AI agents rely on them for tool selection and usage. Unlike human-facing code, agents need rich descriptions to understand capabilities and constraints. This is critical for vendor-neutral AI agent ecosystems.

Tool Documentation Standards

Docstring Structure

MCP tool docstrings serve as API documentation for AI agents. They must be comprehensive:

@mcp.tool
async def kubectl(args: str) -> str:
    """Execute kubectl commands for Kubernetes cluster management.

    Use this tool for all kubectl operations. Provide the kubectl
    arguments as a single string (e.g., "get pods -n default").

    **Important:** This tool requires kubectl to be installed and
    configured with cluster access. Commands are executed with the
    current user's kubeconfig context.

    Args:
        args: kubectl command arguments as a single string.
              Examples:
              - "get pods -n default"
              - "apply -f deployment.yaml"
              - "logs pod-name -n namespace --tail=100"

    Returns:
        JSON string with structure:
        {
            "stdout": "command output",
            "stderr": "error output (empty if success)",
            "statusCode": 0
        }

        Status codes:
        - 0: Success
        - 1: General error
        - 2: Misuse of command

    Raises:
        RuntimeError: If kubectl is not installed or not in PATH

    Example:
        >>> result = await kubectl("get pods -n default")
        >>> data = json.loads(result)
        >>> print(data["stdout"])
        NAME                    READY   STATUS    RESTARTS   AGE
        pod-123                 1/1     Running   0          5m
    """

Read the full file on GitHub · 702 lines

Changes

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.

  1. 6d ago First seen · 702 lines · 17 tokens per session scan C 13fae2e5a397

Subscribe to this mod's changes

510-mcp-servers is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (17 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 4,511 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.