Use case · Developers

Eyrie for developers.

For engineers who track architecture decisions, debug threads, and learning notes in Markdown — and want their existing AI tools (Cursor, Claude Code, Windsurf, Zed) to read those notes as project context. Eyrie is the bridge between your scratch folder and your coding agent.

The dev-specific superpower: MCP everywhere.

Eyrie ships an MCP server that exposes your notes folder to any MCP-aware coding tool. One click installs it into:

• Cursor — your IDE can pull spec docs, ADRs, and debug notes as context for code generation.
• Claude Code — Anthropic's CLI agent can read your notes folder when refactoring.
• Windsurf — Cascade agent reads your notes alongside your codebase.
• Zed — native-fast editor with MCP support.
• Continue — VS Code / JetBrains extension.
• Cline — open-source autonomous agent.

Build a note once. Every tool that supports MCP can read it. Full MCP client guide →

What engineers actually keep in Markdown.

ADRs (Architecture Decision Records).

One .md file per decision: title, context, decision, consequences. Six months later, when someone (or you) asks "why did we go with Postgres over MySQL?", the answer is in 0042-database-choice.md. Eyrie's chat panel surfaces ADRs by topic without you remembering filenames.

Debug threads.

Long-form troubleshooting sessions — the symptom, what you tried, what didn't work, what eventually fixed it. Engineering teams have known for years that these are gold; few teams actually keep them. Eyrie's auto-categorization tags them so the next time you hit a similar symptom, semantic search finds the previous resolution.

Learning notes.

You read a paper on consensus algorithms, a deep-dive on Postgres internals, a blog post on rate-limiting strategies. Eyrie's vault holds all of them. AI surfaces "what have I read about X?" when you're about to build it.

Project-specific scratch.

Per-project folders with running notes — pre-mortems, scope-creep tracking, what you'll tell the boss on Monday. Useful between sprints, indispensable on retros.

Connecting Eyrie to your IDE.

Two-minute setup:

1. Install Eyrie and open your notes folder.
2. Settings → MCP. Eyrie detects which clients you have (Cursor, Claude Desktop, Windsurf, etc.).
3. Click "Install" next to each. Eyrie writes the right config into each tool's settings file.
4. Restart the IDE. Eyrie's tools show up in its MCP tool list — search_notes, get_backlinks, fetch_url, apply_edit.
5. Use your IDE normally. When your AI prompt needs notes context, the agent calls Eyrie's tools.

See how to use Claude Desktop with your Markdown notes → for the full walkthrough.

The honest comparison vs other dev notes tools.

The trade-off vs IDE-only.

Some engineers prefer keeping notes inside their codebase (a docs/ folder, ADRs in the repo). That's a defensible choice — the notes live with the code. Eyrie's argument: your cross-project notes don't belong in any one repo. Architecture patterns you've learned, performance debugging templates, libraries you wish someone else had built — those want a vault, not a repo.