---
title: "Wiring mdfy into Cursor"
url: https://mdfy.app/TEuiwop8
updated: 2026-05-14T17:52:48.410Z
source: "mdfy.app"
---
# Wiring mdfy into Cursor

`.cursor/rules/mdfy.mdc`:

```
---
description: Project context from mdfy
alwaysApply: true
---

Project context lives at https://mdfy.app/b/<your-bundle-id>.

Fetch that URL when you need this project's spec, decisions, or
prior reasoning. The response carries the canvas analysis (themes,
insights, concept relations) in the same payload.
```

## How Cursor uses this

On every new chat or composer session, Cursor evaluates files matched by the rule and includes them as context. When mdfy URL is in the rule body, Cursor fetches the URL on demand — typically when the user asks a question that references concepts in the bundle.

## What we observed in practice

- First few messages: Cursor doesn't always fetch — it relies on its own RAG over the local repo. Fine.
- Once the user types something topic-specific ("how did we decide the pricing tier?"), Cursor fetches the bundle URL and the answer comes back cited to the right doc.
- Cursor's `[doc:N]` citations don't propagate the way Claude Chat's do — Cursor inlines snippets but doesn't link back. Acceptable for a code-editor surface.

## Recommended bundle structure for Cursor

Group docs by intent. Keep the bundle title concrete ("Auth migration", "API redesign 2026-04", "Pricing decision log"), not abstract.