Skip to content
MCP-Bridge

Submit .cursorrules Configuration

Contribute high-quality prompt rules, context specifications, and developer guidelines to help thousands of developers build faster with Cursor AI and Model Context Protocol (MCP).

Submission Workflow

  1. 1.
    Open a GitHub Issue: Use our standardized submission issue template on the official repository. Provide a title formatted as [Rule Submission]: Framework/Language Name.
  2. 2.
    Paste Rule Content & Spec: Copy your complete .cursorrules block or MDC rule definitions. Include explanations of patterns, code conventions, and edge cases covered.
  3. 3.
    Automated Review & Indexing: Our automated continuous integration checks rule structure, formatting, token bounds, and safety standards before community maintainers merge and publish to the live directory.
Open Submission Issue →

Submission Guidelines & Standards

To ensure all community-contributed rules deliver maximum value to developers and maintain high inference accuracy in Cursor AI, submitted rule sets must adhere to strict quality criteria:

  • •Framework Specificity: Rules must target a concrete framework, programming language, runtime, or architectural pattern (e.g., Next.js App Router, FastAPI, Rust Tokio, Supabase RLS).
  • •Actionable Directives: Use explicit imperative instructions (e.g., "Use server actions for mutation") rather than passive descriptions. Avoid ambiguous recommendations.
  • •Token Efficiency: Keep rule definitions concise and structured. Avoid verbose narrative essays that exhaust context windows unnecessarily.
  • •Safety & Security: Configurations must not include hardcoded API keys, private credentials, malicious commands, or instructions that bypass security checks.
  • •Open Source License: Submitting a rule configuration automatically places it under the MIT License for public community access.

Rule Structure Specification

Recommended layout for submitting .cursorrules files. Structuring your submission with clear headings helps Cursor AI parse section priorities effectively:

# [Framework Name] Project Guidelines

## Code Style & Formatting Rules

- Prefer functional components and strict TypeScript interfaces.

- Use kebab-case for filenames and PascalCase for React components.

## Architecture & File Layout

- Co-locate feature components in feature-based directory structures.

## Common Anti-Patterns to Avoid

- Never bypass type safety with explicit `any` declarations.

Validation & Quality Assurance Criteria

Every pull request and issue submission passes through automated validation passes prior to approval:

Syntax & Format Check

Validates markdown formatting, code block syntax highlighting specs, and structural section headers.

Token Budget Check

Ensures total token length remains within optimal context limits (typically under 1,500 tokens).

Duplication Check

Verifies that the submitted rule set presents original utility and does not duplicate existing directory entries.

MCP Compatibility

Ensures referenced MCP server protocols or tools align with official Model Context Protocol standard schemas.

Governance & Maintenance Process

MCP-Bridge is maintained as a community-driven open directory. Rules are reviewed by domain maintainers within 48 hours of submission. Once approved, the rules are compiled, assigned a canonical URL, and made available for instant 1-click download or automated injection into developer toolchains. Authors receive contributor attribution on the rule detail page.

Submission FAQ

How long does the submission review process take?

Most submissions are reviewed and verified by community maintainers within 24 to 48 hours. You will receive updates directly on your GitHub issue or pull request.

Can I update an existing rule configuration?

Yes! Submit an issue or pull request referencing the existing rule ID. Detail what updates were made (e.g. updating for Next.js 15 or Tailwind v4) and why the changes improve code generation quality.

What is the difference between .cursorrules and MDC rule formats?

.cursorrules files provide project-wide rules in a single file at the repository root. MDC format rules allow modular, file-specific rule scoping within the .cursor/rules/ folder. We accept and support both formats.

Are commercial framework rules accepted?

We welcome rules for both open-source and commercial frameworks, provided the rule file content itself contains no proprietary code and is released under MIT for community use.

Suggest an API

Missing an API or custom service in our directory? Use our API suggestion template to request a new Model Context Protocol translation or configuration builder.

Suggest an API →