MCP server for EventCatalog
Most team communication work still happens through a UI a human drives. 📖 EventCatalog MCP server moves it into the conversation instead. MCP server for EventCatalog.
The server publishes 10 tools. What each one is for:
find_resources — Find resources that are available in EventCatalog including services, domains, events, commands, queries, flows, entities, channels, teams, usersfind_resource — Get more information about a service, domain, event, command, query, flow, entity, or channel in EventCatalog using its id and versionfind_owners — Find owners (teams or users) for a domain, service, message, event, command, query, flow, or entity in EventCatalogfind_producers_and_consumers — Get the producers (sends) and consumers (receives) for services in EventCatalogget_schema — Returns the schema for a service (e.g., OpenAPI, AsyncAPI, GraphQL), event, command, or query in EventCatalogreview_schema_changes — Reviews schema changes for breaking changes and suggests fixesexplain_ubiquitous_language_terms — Explain ubiquitous language terms for a given domaincreate_flow — Create a new flow in EventCatalog given a description of the business workfloweventstorm_to_eventcatalog — Turn a photo of an EventStorm session into an EventCatalogcreate_eventcatalog — Create a new EventCatalog project from scratchConfiguration is passed through the environment: LICENSE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. 📖 EventCatalog's toolset — find_resources, find_resource, find_owners and 7 more — is a fair guide to whether it matches your workflow. It is maintained by event-catalog; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against 📖 EventCatalog's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| find_resources | Find resources that are available in EventCatalog including services, domains, events, commands, queries, flows, entities, channels, teams, users, and docs |
| find_resource | Get more information about a service, domain, event, command, query, flow, entity, or channel in EventCatalog using its id and version |
| find_owners | Find owners (teams or users) for a domain, service, message, event, command, query, flow, or entity in EventCatalog |
| find_producers_and_consumers | Get the producers (sends) and consumers (receives) for services in EventCatalog |
| get_schema | Returns the schema for a service (e.g., OpenAPI, AsyncAPI, GraphQL), event, command, or query in EventCatalog |
| review_schema_changes | Reviews schema changes for breaking changes and suggests fixes |
| explain_ubiquitous_language_terms | Explain ubiquitous language terms for a given domain |
| create_flow | Create a new flow in EventCatalog given a description of the business workflow |
| eventstorm_to_eventcatalog | Turn a photo of an EventStorm session into an EventCatalog |
| create_eventcatalog | Create a new EventCatalog project from scratch |
{
"mcpServers": {
"eventcatalog": {
"command": "npx",
"args": ["-y", "tsx /PATH_TO_YOUR_REPO/src/index.ts", "https://demo.eventcatalog.dev", "ABCD-1234-5678-9012-3456-7890"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LICENSE_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.