EventCatalog MCP Server

The EventCatalog MCP Server bridges the gap between an AI assistant and a live, richly‑structured event‑driven architecture. By exposing the EventCatalog data model through the Model Context Protocol, developers can query their domains, services, messages, and associated schemas directly from tools like Claude, Cursor, or Windsurf. This eliminates the need to manually sift through documentation or run separate API calls, enabling instant, context‑aware insights during code reviews, design discussions, or stakeholder conversations.

At its core, the server connects to an EventCatalog instance—an open‑source platform that visualizes and documents event‑driven systems, hosts OpenAPI/AsyncAPI specifications, and maps out domains and services. Once the server is running locally or in a cloud environment, any MCP‑compliant client can send natural‑language queries. The server translates these into structured requests against the EventCatalog graph, retrieves relevant entities (e.g., a service’s ownership, an event schema, or the message flow between services), and returns concise answers. For developers, this means being able to ask questions like “Who owns the event?” or “Show me the JSON schema for the command” and receive an immediate response without leaving their IDE or chat interface.

Key capabilities include:

• Real‑time schema retrieval for OpenAPI, AsyncAPI, and JSON Schema definitions.
• Architecture exploration, such as discovering relationships between domains, services, and messages.
• Ownership and responsibility mapping to identify who owns which components.
• Zero‑code integration with popular MCP clients, allowing instant access from within the user’s preferred workflow.

Typical use cases span a broad spectrum:

• Architects can validate design decisions on the fly, ensuring that event contracts remain consistent.
• Developers can quickly locate the correct API endpoint or message format while writing code, reducing context switches.
• Stakeholders can pose business‑level questions about system ownership or data flows directly from a chat interface, fostering clearer communication.

By leveraging the MCP protocol, the EventCatalog server offers a unique advantage: it unifies disparate tools under a single conversational umbrella, turning static documentation into an interactive knowledge base that scales with the team’s tooling ecosystem.