core-development

A project rulebook for developing the Cycloid MCP server, a Python server that provides tools to AI assistants. It defines how tools, errors, types, logging, imports, and command-line results should be handled.

In plain words
What is it for?
It guides assistants when adding server components, injecting command-line access, defining typed inputs and outputs, handling tool errors, organizing imports, and returning JSON.
Why use it?
It keeps new code consistent with the server's architecture and FastMCP 3.0 conventions. This helps avoid unsupported patterns such as unnecessary base classes or direct command-line setup.

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/cycloidio/cycloid-mcp-server/core-development
Clone the repo
git clone --depth 1 https://github.com/cycloidio/cycloid-mcp-server

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 658 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00658
Opus 5 $0.00000 $0.00329
Sonnet 5 $0.00000 $0.00132
Haiku 4.5 $0.00000 $0.00066

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

Security

Grade A, and why

core-development 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/core-development.mdc · 61 lines

What it actually says

You are an expert in Python backend development for the Cycloid MCP Server using FastMCP 3.0.

Key Principles

  • Use standalone @tool() and @resource() decorators (not class-based MCPMixin)
  • Inject CLIMixin via Depends(get_cli) from src.dependencies
  • Use ToolError from fastmcp.exceptions for tool-level errors
  • Leverage centralized type definitions from src.types
  • Apply proper import organization (stdlib → third-party → local)
  • JSON-only output (no table formatting)
  • Follow FastMCP logging with get_logger from fastmcp.utilities.logging

Core Development Guidelines

  1. Architecture Patterns

    • Components are plain async functions in src/components/ — auto-discovered by FileSystemProvider
    • No base classes, no MCPMixin, no ComponentRegistry
    • CLI injection via Depends(get_cli) — never instantiate CLIMixin directly in tools
    • Use execute_cli_command with auto_parse parameter for CLI calls
    • Use process_cli_response for standardized response processing
  2. Type Safety & Imports

    • Import common types from src.types (JSONDict, JSONList, CliFlags, OptionalString, etc.)
    • Import order: stdlib → third-party → local (src.)
    • FastMCP Depends import needs # type: ignore[reportAttributeAccessIssue]
    • Depends(get_cli) defaults need # type: ignore[reportCallInDefaultInitializer]
  3. Error Handling

    • Use ToolError from fastmcp.exceptions for validation errors, not-found, etc.
    • Use CycloidCLIError from src.exceptions for CLI execution failures
    • Log with get_logger(__name__) from fastmcp.utilities.logging
  4. CLI Integration

    • Use execute_cli_command with auto_parse=True for parsed JSON responses
    • Use execute_cli_command with auto_parse=False for raw CLIResult
    • Use process_cli_response for consistent response handling
    • Never cache CLI API responses (dynamic data)
    • Output format is always JSON (hardcoded --output json)
  5. Testing

    • Use pytest + pytest-asyncio with FastMCP's Client
    • Register functions via server.add_tool() / server.add_resource()
    • Mock CLIMixin with @patch and AsyncMock
    • Tool errors raise ToolError exceptions in client
  6. Code Quality

    • Pyright strict mode (pyrightconfig.json)
    • black (88 char), isort (black profile), flake8 (100 char max)
    • Python 3.12+ (CI runs 3.13)

Dependencies

  • Python 3.12+
  • FastMCP 3.0+
  • pytest, pytest-asyncio
  • pyright, flake8, black, isort
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 · 61 lines · 658 tokens per session scan A ba577906421b

Subscribe to this mod's changes

core-development is a cursor rule published in the GitHub repository cycloidio/cycloid-mcp-server (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 658 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.