Cursor

Overview

Cursor + EventCatalog gives you a powerful new way to interact with your architecture using natural language in your IDE.

Ask questions about your architecture directly in Cursor, and give Cursor the context it needs to answer your questions.

This integration works seamlessly with MCP (Model Catalog Protocol), allowing Cursor to read your architecture documentation.

Example Prompts

Here are a few useful questions you or your team can ask Cursor once integrated:

• “Which services produce the InventoryAdjusted event?”
• “Who owns the OrderService?”
• “What commands does the Payments domain support?”
• “How is UserSignedUp consumed across the system?”
• “What are all the events in the Checkout flow?”
• "Create a new event schema following our best practices documented in EventCatalog"

Cursor can return answers with summaries, links to documentation, and even visual guidance using EventCatalog data.

Value for Teams

This integration can save time and unlock new workflows:

For Developers
No more context switching—get architecture answers instantly, even while coding or debugging.

For New Hires
Ramp up faster by asking natural-language questions about the system instead of navigating complex docs.

Save time: Stop searching through repositories, find the right documentation, and get answers to your questions. Save money: Reduce support overhead and onboarding time across the team.
Bridge silos: Make architecture accessible across roles and departments. Improve quality: Ensure that your architecture is consistent and follows best practices.

How It Works

Cursor connects to your EventCatalog instance via the MCP protocol. It reads your architecture models—schemas, services, events, domains—and provides conversational answers.

Core Features

• Ask Cursor anything about your system architecture
• Cursor queries your EventCatalog using the MCP protocol
• Supports semantic architecture models—domains, services, events, commands, ownership, and more
• Works with synced schemas from GitHub, schema registries, and other sources
• Enables cross-functional teams to understand architecture effortlessly