project-rules

A set of project rules for building Python-based AI-agent projects and MCP servers. MCP, or Model Context Protocol, is a way for AI applications to connect to external tools and data.

In plain words
What is it for?
Use it when creating an MCP server for Google Drive, Google Docs, or Google Sheets with Python, uv, and the MCP package.
Why use it?
It keeps dependency management, documentation, server structure, and framework choices consistent across a project.

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/adexltd/mcp-google-suite/project-rules
Clone the repo
git clone --depth 1 https://github.com/adexltd/mcp-google-suite

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,550 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.02550
Opus 5 $0.00000 $0.01275
Sonnet 5 $0.00000 $0.00510
Haiku 4.5 $0.00000 $0.00255

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

Security

Grade A, and why

project-rules 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/project-rules.mdc · 302 lines

How it starts

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

Your rule content

Assume you are a Sr software engineer who has an experience in developing AI agents, experience with python.

Important Rules

Instructions

Based on the project requirement document create me a MCP server for google drive , docs and sheets operations. use @https://github.com/modelcontextprotocol/python-sdk?tab=readme-ov-file#core-concepts as an example and for creating MCP server no need to use other frameworks like Fast API

MCP low level server defination

""" MCP Server Module

This module provides a framework for creating an MCP (Model Context Protocol) server. It allows you to easily define and handle various types of requests and notifications in an asynchronous manner.

Usage:

  1. Create a Server instance: server = Server("your_server_name")

  2. Define request handlers using decorators: @server.list_prompts() async def handle_list_prompts() -> list[types.Prompt]: # Implementation

    @server.get_prompt() async def handle_get_prompt( name: str, arguments: dict[str, str] | None ) -> types.GetPromptResult: # Implementation

    @server.list_tools() async def handle_list_tools() -> list[types.Tool]: # Implementation

    @server.call_tool() async def handle_call_tool( name: str, arguments: dict | None ) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]: # Implementation

    @server.list_resource_templates() async def handle_list_resource_templates() -> list[types.ResourceTemplate]: # Implementation

  3. Define notification handlers if needed: @server.progress_notification() async def handle_progress( progress_token: str | int, progress: float, total: float | None ) -> None: # Implementation

  4. Run the server: async def main(): async with mcp.server.stdio.stdio_server() as (read_stream, write_stream): await server.run( read_stream, write_stream, InitializationOptions( server_name="your_server_name", server_version="your_version", capabilities=server.get_capabilities( notification_options=NotificationOptions(), experimental_capabilities={}, ), ), )

    asyncio.run(main())

The Server class provides methods to register handlers for various MCP requests and notifications. It automatically manages the request context and handles incoming messages from the client. """

Read the full file on GitHub · 302 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 · 302 lines · 0 tokens per session scan A 9ad9315376e2

Subscribe to this mod's changes

project-rules is a cursor rule published in the GitHub repository adexltd/mcp-google-suite (3 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,550 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.