Skip to content
MARKO DOCS

Cursor

Cursor is an AI-first code editor built on VS Code. devai:install configures it with a .cursor/rules/marko.mdc project rules file and MCP server registration.

Prerequisites

Section titled “Prerequisites”

What devai:install writes

Section titled “What devai:install writes”

Running marko devai:install with Cursor detected produces the following files:

.cursor/rules/marko.mdc            # Project guidelines and conventions (alwaysApply: true)
.cursor/mcp.json                   # MCP server registration (marko mcp:serve)
AGENTS.md                          # Shared guidelines file (devai-managed marker block)

Cursor does not implement LSP registration and no skills are distributed for Cursor.

.cursor/rules/marko.mdc

Section titled “.cursor/rules/marko.mdc”

The .cursor/rules/marko.mdc file is written with alwaysApply: true frontmatter so it is always included in Cursor’s context. The YAML frontmatter stays the first line of the file; the devai-managed guidelines sit below it inside a <!-- BEGIN/END marko:devai --> marker block, so you can add your own rules outside the markers without losing them on re-run. It contains merged Marko guidelines:

  • Module structure and naming conventions
  • Available MCP tools and usage patterns
  • Project-specific guidelines from every installed package’s resources/ai/guidelines.md

MCP registration

Section titled “MCP registration”

The .cursor/mcp.json file registers marko mcp:serve as an MCP server using the mcpServers key. Cursor’s AI can invoke tools like find_event_observers and validate_module during chat and Composer sessions.

AGENTS.md

Section titled “AGENTS.md”

devai:install writes the shared AGENTS.md guidelines inside a <!-- BEGIN/END marko:devai --> marker block: created if absent, and on later runs only the marked region is refreshed, so content you add outside the markers is preserved. Remove the markers to take full ownership — devai then leaves the file alone. See Editing generated files.

Manual verification

Section titled “Manual verification”
  1. Open your project in Cursor.
  2. Open the AI chat panel and ask: What Marko MCP tools are available?
  3. Ask: Search Marko docs for "events" — search_docs should return results if a docs driver is installed.
  4. Confirm .cursor/rules/marko.mdc exists and contains alwaysApply: true.
  5. Check that .cursor/mcp.json references marko mcp:serve under mcpServers.

Agent-specific tips

Section titled “Agent-specific tips”
  • Composer sessions: Use Cursor’s Composer for multi-file Marko tasks. The validate_module tool lets it verify its own output before presenting it to you.
  • MCP in chat: Type @mcp in the Cursor chat to surface available MCP tools. The Marko tools appear automatically once .cursor/mcp.json is in place.

Package READMEs

Section titled “Package READMEs”