---
title: "Wiring mdfy into Cursor"
url: https://memory.wiki/TEuiwop8
updated: 2026-05-14T17:52:48.410Z
hub: https://memory.wiki/hub/demo
bundle_count: 2
concept_count: 12
source: "memory.wiki"
---
# 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.


---

## Concepts in this document
- **mdfy** _(entity)_
  A tool that stores project context and decision history, integrated into Cursor via custom rules.
- **Structural moat** _(concept)_
  The defensible advantage created by mdfy's vendor-neutral positioning, which competitors cannot replicate due to inherent conflicts of interest.
- **Claude** _(entity)_
  Anthropic's AI model cited as an example of vendor lock-in through projects and memory features.
- **bundle URL** _(entity)_
  The delivery mechanism for markdown digests that now carries embedded graph analysis instead of doc list only
- **AI tool integration** _(concept)_
  Ability to paste hub URL directly into Claude, ChatGPT, Cursor, or Codex for question-answering against the hub.
- **Cursor IDE** _(entity)_
  Code editor that can fetch and utilize mdfy bundle URLs for project context.
- **Cursor** _(entity)_
  Code editor that consumes mdfy bundles as context for chat and composer sessions.
- **mdfy Platform** _(entity)_
  Knowledge management platform designed for AI-first workflows with URL-based sharing.
- **ChatGPT** _(entity)_
  Example of an AI provider whose memory feature is intentionally confined to its own product.
- **Claude Code** _(entity)_
  AI coding feature mentioned as a primary context for AI-native developer adoption.
- **Codex CLI** _(entity)_
  Command-line interface that integrates with AGENTS.md to load project context and caches configuration at session start.
- **AI Integration** _(tag)_
  Artificial intelligence features and infrastructure including vector search and multi-provider setup.

## Concept relations (within this doc's concepts)
- **Cursor IDE** fetches **bundle URL**
- **mdfy** integrates with **Claude**
- **mdfy** solves problem for **ChatGPT**
- **mdfy** integrates with **Cursor**
- **mdfy** integrated into **Cursor**

## Bundles containing this document
- [Engineering decisions + cross-AI strategy](https://memory.wiki/b/8IkpnVgX)
  > A working bundle: the ADR for shipping graph_data in URLs, the cross-AI moat argument, and a hands-on integration note for Cursor. Three docs that explain *what we're building and why* in 10 minutes o
- [AI tool integration tour](https://memory.wiki/b/EJbI7cto)
  > Claude Code, Codex (AGENTS.md), MCP server, Cursor — every wiring path the demo hub supports.

_Hub canonical:_ https://memory.wiki/hub/demo
_Concept digest:_ https://memory.wiki/raw/hub/demo?digest=1&compact=1