EventCatalog MCP Server provides a standardized interface for AI assistants to interact with event-driven architecture metadata and resources. Built by David Boyne, it enables querying and retrieving information about events, services, domains, queries, commands, and other architectural components through a set of predefined tools and resources. The server dynamically loads catalog information and supports schema retrieval, making it particularly useful for developers and architects seeking to understand and explore complex event-driven systems.
暂无评论. 成为第一个评论的人!
登录以参与讨论
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, and includes pagination support with cursors.
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 (teams or users) for a domain, service, message, event, command, query, flow, or entity in EventCatalog. Returns detailed owner information with documentation links.
Get the producers (sends) and consumers (receives) for services in EventCatalog. Helps understand message flow and service dependencies.
Returns the schema for a service (e.g., OpenAPI, AsyncAPI, GraphQL), event, command, or query in EventCatalog. Supports all major schema formats.
Reviews schema changes for breaking changes and suggests fixes. Compares old and new schemas to identify potential issues and provides recommendations for handling breaking changes.
Explain ubiquitous language terms for a given domain. Returns definitions and context for domain-specific terminology.
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.
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 a new EventCatalog project from scratch. Generates all necessary configuration files (package.json, eventcatalog.config.ts) and sets up the complete folder structure and initial documentation.