A server that connects MCP clients (Claude, Cursor, Windsurf, etc.) to EventCatalog instances, allowing users to ask questions about their event-driven architecture and get insights about domains, services, and message schemas directly within their development tools.
Get insights from your EventCatalog directly from your MCP Client (Claude, Cursor, Windsurf, etc)
Features: Ask about domains, services and messages. Get answers in seconds. Request schemas, who owns what and much more.
[Read the Docs](https://www.eventcatalog.dev/docs/development/getting-started/introduction) | [View Demo](https://demo.eventcatalog.dev)
? Run MCP server locally on your machine with one command
? Connect to your EventCatalog instances
? Ask questions about your architectures
? Ask questions about your OpenAPI and AsyncAPI specifications
? Ask about domains, services and messages, and much more
? Get the schemas for events, queries, commands and services (OpenAPI, AsyncAPI, JSON Schema)
Using AI to get more value from EventCatalog
EventCatalog is an Open Source tool that helps you document your event-driven architecture.
Using EventCatalog you can document your domains, services and messages, schemas and much more.
EventCatalog will visualize your architecture for you all, provide the ability to add semantic meaning for stakeholders, host your OpenPAI and AsyncAPI specifications and integrate with any broker in the world.
Using the EventCatalog MCP Server you can get more value from your EventCatalog by asking questions about your architecture in the tools you already use.
Developers can integrate the MCP server with MCP supported IDES (e.g Cursor, Windsurf)
Stakeholders can ask questions about your architecture in the tools they use (e.g Claude)
If you are using tools that do not support the MCP protocol, you can still use the llms.txt standard to integrate with other LLLM tools (e.g Gemini, GPT-4)
Getting Started
Installation
First, you need to enable the LLMS.txt feature in your EventCatalog instance.
Enable the LLMS.txt feature in your EventCatalog instance, by configuring your eventcatalog.config.js file.
Deploy your EventCatalog instance with the LLMS.txt feature enabled.
Setup MCP Clients
Each MCP client has a different way of adding the MCP server.
You can find some helpful links below to get started.
To use this with Claude Desktop, add the following to your claud_desktop_config.json file. The full path on MacOS: ~/Library/Application Support/Claude/claud_desktop_config.json, on Windows: %APPDATA%Claudeclaud_desktop_config.json