cursorrules

A set of coding rules for a Python server that lets AI agents manage UniFi network infrastructure through the Model Context Protocol, a standard way to expose tools and data to AI systems.

In plain words
What is it for?
Use it when developing or reviewing this UniFi integration, including tools for devices, networks, clients, firewalls, Wi-Fi, traffic data, and read-only resources.
Why use it?
It gives the project consistent expectations for asynchronous code, validation, testing, security checks, caching, webhooks, and support for multiple UniFi sites.

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/enuno/unifi-mcp-server/cursorrules
Clone the repo
git clone --depth 1 https://github.com/enuno/unifi-mcp-server

Made for: Cursor.

Per session 2,471 This file is loaded in full into every session.
When invoked 2,471 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.02471 $0.02471
Opus 5 $0.01236 $0.01236
Sonnet 5 $0.00494 $0.00494
Haiku 4.5 $0.00247 $0.00247

Measured 2d ago against content hash 4ccebf748bf8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.cursorrules · 307 lines

How it starts

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

Cursor Rules for UniFi MCP Server

You are an expert Python developer working on a production-grade MCP (Model Context Protocol) server for UniFi Network Controller integration. This server enables AI agents to manage UniFi network infrastructure through 40+ standardized tools.

Project Context

Technology Stack:

  • Python 3.10+ with type hints and async/await patterns
  • FastMCP framework for MCP server implementation
  • Pydantic for data validation and schema generation
  • Redis for optional caching layer
  • pytest for testing (target 80%+ coverage)
  • Pre-commit hooks: black, isort, ruff, mypy, bandit

Architecture:

  • Async-first design for high concurrency
  • Tool-based API (40+ MCP tools across devices, networks, clients, firewall, WiFi, DPI)
  • Resource endpoints for read-only data access
  • Optional Redis caching with automatic invalidation
  • Webhook support for real-time event handling
  • Multi-site UniFi controller support

Project Structure:

unifi-mcp-server/
├── src/
│   ├── main.py              # MCP server registration and entry point
│   ├── api/                 # UniFi API client with rate limiting
│   ├── tools/               # MCP tool implementations (grouped by domain)
│   ├── resources/           # MCP resource definitions
│   ├── webhooks/            # Event handlers
│   ├── config/              # Configuration management
│   ├── utils/               # Validators, formatters, helpers
│   └── cache.py             # Redis caching implementation
├── tests/
│   ├── unit/                # Fast, isolated tests with mocks
│   └── integration/         # Tests requiring UniFi controller
├── docs/
│   └── AI-Coding/           # AI coding guidelines
├── .env.example             # Environment variable template
└── pyproject.toml           # Dependencies and project config

Core Coding Principles

1. Async-First Development

  • ALWAYS use async def for functions that perform I/O operations
  • Use await for API calls, database queries, file operations, HTTP requests
  • Leverage asyncio.gather() for concurrent operations
  • Use async with for context managers (UniFi client, Redis connections)
  • NEVER use blocking synchronous calls in async contexts
  • Consider using anyio.to_thread.run_sync() for CPU-intensive operations

Read the full file on GitHub · 307 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. 2d ago First seen · 307 lines · 2,471 tokens per session scan A 4ccebf748bf8

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository enuno/unifi-mcp-server (242 stars, last pushed 14d ago), licensed Apache-2.0. It adds 2,471 tokens to every session, about $0.0124 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.