TalkEventsToMe

What is TalkEventsToMe?

TalkEventsToMe is a learning project that integrates with EventCatalog via an MCP (Model Context Protocol) server, enabling AI assistants such as Claude, Cursor, and Windsurf to query an organization's EventCatalog instance for insights about event-driven architecture.

How to use TalkEventsToMe?

Configure the MCP server using the provided .mcp.json file (requires an EventCatalog Scale license key), install dependencies automatically via npx, and restart the MCP-compatible client (e.g., Cursor) to load the server. Verify by asking questions about your event catalog.

Key features of TalkEventsToMe

• Integrates with EventCatalog via MCP protocol
• Provides tools like find_resources, find_resource, find_producers_and_consumers, get_schema, review_schema_changes, and explain_ubiquitous_language_terms
• Exposes resources for all messages, events, domains, services, queries, commands, flows, teams, and users
• Works with Claude, Cursor, Windsurf, and other MCP-compatible clients
• Designed for learning and exploration of event-driven architecture

Use cases of TalkEventsToMe

• Discover which team owns a specific event in your architecture
• Understand event flows and dependencies when a menu gets published
• Learn how to register a new event with EventCatalog and notify subscribers
• Explore error‑handling and reliability patterns for event delivery failures

FAQ from TalkEventsToMe

What runtime or dependencies are required?

You need an EventCatalog Scale license key (a 14‑day trial is available from EventCatalog Cloud), and the MCP server is installed automatically via npx.

Where does the data live and how is it accessed?

The EventCatalog instance is hosted at https://eventcatalog.compassdigital.org/ and is protected by Google OAuth. You must have network access and be authenticated.

What tools does the MCP server expose?

It provides six tools: find_resources, find_resource, find_producers_and_consumers, get_schema, review_schema_changes, and explain_ubiquitous_language_terms.

What transports or authentication methods are supported?

The server uses the MCP protocol with standard HTTP transport to the EventCatalog instance. Authentication is handled via Google OAuth for the instance and an EventCatalog Scale license key for the server.

Are there known limitations?

The EventCatalog instance is protected by Google OAuth and requires a valid, non‑expired Scale license key. The project is intended for learning and exploration, not production use.