agentleFS
sandraschisandraschi/songgeneration-mcp/.cursor/rules/mcp-sota-standards.mdc

songgeneration-mcp / rules

Cursor rule4 starsChanged 32 days agoMITView on GitHub

Ensure all MCP development follows SOTA Standards for documentation, response patterns, and architectural consistency.

We split this mcp-sota-standards.mdc into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    FastMCP Compliance: Use FastMCP 2.14.1+ standards for tool families, portmanteau patterns, and structured returns.

    line 19
  2. Distinctive:

    When implementing new tools or modifying server logic, always ensure compliance with the centralized standards to maintain the "neural …

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
mcp-sota-standards.mdc
---
description: Ensure all MCP development follows SOTA Standards for documentation, response patterns, and architectural consistency.
globs: ["**/*.py", "**/*.md", "**/*.json", "**/mcp_server.py"]
alwaysApply: true
---

# MCP SOTA Standards (Centralized)

This repository follows the Model Context Protocol (MCP) SOTA standards managed in the `mcp-central-docs` repository.

## Core References
- [STANDARDS.md](file:///d:/Dev/repos/mcp-central-docs/STANDARDS.md)
- [gemini.md](file:///d:/Dev/repos/mcp-central-docs/gemini.md)
- [cursor.md](file:///d:/Dev/repos/mcp-central-docs/docs/ecosystem/cursor/README.md)

## Key Requirements
1. **Config & Log Locations**: Refer to Section 2.3 in [STANDARDS.md](file:///d:/Dev/repos/mcp-central-docs/STANDARDS.md) for standardized Windows paths.
2. **Startup Diagnostics**: Section 2.3 contains crucial paths for debugging startup failures (e.g., `%APPDATA%\Claude\logs` or `%APPDATA%\Cursor\logs`).
3. **FastMCP Compliance**: Use FastMCP 2.14.1+ standards for tool families, portmanteau patterns, and structured returns.

When implementing new tools or modifying server logic, always ensure compliance with the centralized standards to maintain the "neural grid" alignment.

Download now (ZIP)

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository7 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.