Read the Docs | View Demo

Why EventCatalog MCP Server?

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.

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.

Example questions:

• What events do we have in our architecture?

• Tell me more about the {service} service.

• I want to create a new feature that will send emails when a user signs up, what events do we have in our architecture that are related to user signups?

• Get me the schema for the event UserCreated in EventCatalog.

• Here is a new version of the UserCreated schema, what downstream consumers will be affected by this change?

Rather then digging through your architecture to find the answers you need, you can ask the MCP server directly from your MCP Client.

Related MCP server: Mattermost MCP Server

EventCatalog MCP Features

• 🤖 Connect to any MCP Client (Claude, Cursor, Windsurf, etc)

• 🤖 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)

• 🤖 Ask questions about ubiquitous language for any domain and their entities

Getting Started

Installation

First, you need to enable the LLMS.txt in your EventCatalog instance.

1. Enable the LLMS.txt in your EventCatalog instance, by configuring your eventcatalog.config.js file.

2. Deploy your EventCatalog instance with the LLMS.txt feature enabled.

Next, you will need to get a EventCatalog Scale license key, you can get a 14 day trial license key from EventCatalog Cloud.

Installing via Smithery

To install EventCatalog for Claude Desktop automatically via Smithery:

Running as a Docker Container

If you want to run the MCP server as a standalone Docker container (for example, to run it as an HTTP server), see the Docker Deployment Guide.

This is useful for:

• Running the MCP server in production environments

• Deploying as a containerized service

• Running in HTTP mode for integration with multiple clients

• Kubernetes, Docker Swarm, or other container orchestration platforms

Transport Modes

The EventCatalog MCP Server supports two transport modes:

STDIO Mode (Default)

• Uses standard input/output for communication

• Ideal for local development and MCP clients like Claude Desktop and Cursor

• Started automatically when you add the server to your MCP client

• No port exposure needed

• Recommended for: Claude Desktop, Cursor, Windsurf, and other desktop MCP clients

HTTP Mode

• Runs as an HTTP server on a specified port (default: 3000)

• Ideal for production deployments and container environments

• Allows multiple clients to connect to a single server instance

• Includes health check endpoints for monitoring

• Recommended for: Docker deployments, Kubernetes, production environments, and multi-client setups

To use HTTP mode, pass http as the transport parameter:

Or set the MCP_TRANSPORT environment variable to http (see Docker Deployment Guide for details).

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.

• Claude Desktop

• Cursor

Adding the MCP server to Claude Desktop

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%\Claude\claud_desktop_config.json

Adding the MCP server to Cursor

Go to Cursor Settings -> MCP Servers -> Add MCP Server.

• Name: eventcatalog

• Command: npx

• Args: -y @eventcatalog/mcp-server {URL_TO_YOUR_EVENTCATALOG_INSTANCE}

Configuration for your project

You can also create .mcp.json files in your project to configure the MCP server for your project using Cursor.

You can read more about configuration for your project in the Cursor documentation.

API

Here is a list of all the APIs that the MCP server supports.

Tools

• find_resources

  • Find resources that are available in EventCatalog including services, domains, events, commands, queries, flows, entities, channels, teams, users, and docs

  • Supports filtering by type and search terms

  • Includes pagination support with cursors

• find_resource

  • Get more information about a service, domain, event, command, query, flow, entity, or channel in EventCatalog using its id and version

  • Returns complete resource details including specifications, owners, producers, and consumers

• find_owners

  • Find owners (teams or users) for a domain, service, message, event, command, query, flow, or entity in EventCatalog

  • Returns detailed owner information with documentation links

• find_producers_and_consumers

  • Get the producers (sends) and consumers (receives) for services in EventCatalog

  • Helps understand message flow and service dependencies

• get_schema

  • Returns the schema for a service (e.g., OpenAPI, AsyncAPI, GraphQL), event, command, or query in EventCatalog

  • Supports all major schema formats

• review_schema_changes

  • Reviews schema changes for breaking changes and suggests fixes

  • Compares old and new schemas to identify potential issues

  • Provides recommendations for handling breaking changes

• explain_ubiquitous_language_terms

  • Explain ubiquitous language terms for a given domain

  • Returns definitions and context for domain-specific terminology

• create_flow

  • Create a new flow in EventCatalog given a description of the business workflow

  • The tool will check all your resources in EventCatalog to find the best resources to match against the description

  • The flow will be created (markdown file) and can be visualized in EventCatalog

• eventstorm_to_eventcatalog

  • Turn a photo of an EventStorm session into an EventCatalog

  • Automatically generates domains, services, events, commands, flows, and ubiquitous language terms

  • Creates proper folder structure and MDX files with frontmatter

• create_eventcatalog

  • Create a new EventCatalog project from scratch

  • Generates all necessary configuration files (package.json, eventcatalog.config.ts)

  • Sets up the complete folder structure and initial documentation

Resources

Resources provide quick access to collections of data from your EventCatalog. They can be used to get context about your architecture.

• eventcatalog://all

  • All resources in EventCatalog (messages, domains, services, flows, teams, users, etc.)

  • Use this for a complete overview of your architecture

• eventcatalog://events

  • All events in EventCatalog

  • Includes event names, versions, and descriptions

• eventcatalog://commands

  • All commands in EventCatalog

  • View all command messages in your system

• eventcatalog://queries

  • All queries in EventCatalog

  • Access all query messages

• eventcatalog://services

  • All services in EventCatalog

  • Complete list of services with their metadata

• eventcatalog://domains

  • All domains in EventCatalog

  • View domain boundaries and subdomains

• eventcatalog://flows

  • All flows (business processes) in EventCatalog

  • Access workflow definitions and state machines

• eventcatalog://teams

  • All teams in EventCatalog

  • View team information and ownership

• eventcatalog://users

  • All users in EventCatalog

  • Access user profiles and ownership information

Missing an API?

We are working on adding more APIs to the MCP server. If you need something specific, please open an issue and we will add it to the server.

Contributing

1. Clone the repository

2. Run npm install to install the dependencies

3. Run npm run build

Running Tests

To run tests with coverage:

To use the build as your MCP server you can point your MCP client to the dist folder.

Example for Cursor:

License

Usage of this feature is part of the EventCatalog Scale Plan