mcp-server-implementation

A set of rules for implementing MCP servers, which provide tools that other software can call.

In plain words
What is it for?
Use it when creating or updating an MCP server package and connecting its tools to configuration and startup code.
Why use it?
It provides a consistent way to load configuration, check required environment variables, create the server, and register its tools.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/dxheroes/mcp-devtools/mcp-server-implementation
Clone the repo
git clone --depth 1 https://github.com/DXHeroes/mcp-devtools

Made for: Cursor.

Per session 526 This file is loaded in full into every session.
When invoked 526 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00526 $0.00526
Opus 5 $0.00263 $0.00263
Sonnet 5 $0.00105 $0.00105
Haiku 4.5 $0.00053 $0.00053

Measured yesterday against content hash ed659fe48a5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-server-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.

.cursor/rules/mcp-server-implementation.mdc · 94 lines

How it starts

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

MCP Server Implementation Guidelines

When implementing a new MCP server or updating an existing one, follow these guidelines:

@file packages/jira/src/index.ts @file .cursor/rules/core-libraries-usage.mdc @file .cursor/rules/typescript-style.mdc

Server Setup

import { createMcpServer } from "@modelcontextprotocol/server";
import { registerTool1 } from "./tools/tool1";
import { registerTool2 } from "./tools/tool2";
// Import more tools as needed

// Create configuration with proper error handling
const getConfig = (): Config => {
  const required = ["REQUIRED_ENV_VAR1", "REQUIRED_ENV_VAR2"];
  for (const env of required) {
    if (!process.env[env]) {
      console.error(`Missing required environment variable: ${env}`);
      process.exit(1);
    }
  }

  return {
    var1: process.env.REQUIRED_ENV_VAR1,
    var2: process.env.REQUIRED_ENV_VAR2,
    optionalVar: process.env.OPTIONAL_ENV_VAR || "default",
  };
};

// Initialize server
const initServer = async () => {
  try {
    const config = getConfig();
    const server = createMcpServer();

    // Register all tools
    registerTool1(server);
    registerTool2(server);
    // Register more tools

    // Start the server
    server.start();
    console.log("MCP server started successfully");
  } catch (error) {
    console.error("Failed to start MCP server:", error);
    process.exit(1);
  }
};

// Start the server
initServer();

Guidelines

  1. Environment Variables

    • Validate all required environment variables at startup
    • Provide sensible defaults for optional variables
    • Document all environment variables in README
  2. Error Handling

    • Implement proper error handling for server initialization
    • Log meaningful error messages
    • Exit with non-zero code on critical errors
  3. Tool Registration

    • Register each tool from its own module
    • Keep registration code organized and maintainable
    • Use consistent patterns across all tools
  4. Logging

    • Log server start/stop events
    • Include appropriate context in logs
    • Avoid logging sensitive information

Read the full file on GitHub · 94 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. yesterday First seen · 94 lines · 526 tokens per session scan A ed659fe48a5a

Subscribe to this mod's changes

mcp-server-implementation is a cursor rule published in the GitHub repository DXHeroes/mcp-devtools (13 stars, last pushed 1y ago), licensed MIT. It adds 526 tokens to every session, about $0.0026 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.

Related

Other cursor rules, from other repositories

cursorrules

You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.

survivorforge/cursor-rules · 2,136 tokens

rule

AI/ML Python development (PyTorch, scikit-learn).

survivorforge/cursor-rules · 0 tokens

language-agnostic-patterns

Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.

madebyaris/advance-minimax-m3-cursor-rules · 37 tokens

cursor-tools-mastery

Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.

madebyaris/advance-minimax-m3-cursor-rules · 36 tokens

cursor-agent-orchestration

Cursor 3.7 orchestration guide: when to plan, when to delegate, nested subagents, multi-environment handoffs, /best-of-n, and Await for long-running branches.

madebyaris/advance-minimax-m3-cursor-rules · 39 tokens

fable5-reasoning

Fable 5 reasoning protocols: task interpretation, risk-first decomposition, approach selection, interleaved thinking, hypothesis ledgers, premortems, calibration, and the stuck-strategy ladder. Load for complex, ambiguous, or long-horizon tasks, for debugging strategy, or whenever progress stalls.

madebyaris/advance-minimax-m3-cursor-rules · 60 tokens