📖 EventCatalog - MCP Server

Created By
event-cataloga year ago
MCP server for EventCatalog
Overview

What is EventCatalog - MCP Server?

EventCatalog - MCP Server is a tool that allows users to gain insights from their EventCatalog directly through various MCP Clients, enabling interaction with event-driven architectures.

How to use EventCatalog - MCP Server?

To use the MCP Server, you need to enable the LLMS.txt feature in your EventCatalog instance and configure your MCP clients (like Claude or Cursor) to connect to the server.

Key features of EventCatalog - MCP Server?

  • Connect to any MCP Client (e.g., Claude, Cursor, Windsurf)
  • Run the MCP server locally with a single command
  • Query your EventCatalog for domains, services, messages, and schemas
  • Get real-time answers about your architecture

Use cases of EventCatalog - MCP Server?

  1. Developers can integrate the MCP server with supported IDEs to streamline their workflow.
  2. Stakeholders can ask questions about the architecture using familiar tools.
  3. It can be used to document and visualize event-driven architectures effectively.

FAQ from EventCatalog - MCP Server?

  • What is the purpose of the MCP Server?

The MCP Server enhances the EventCatalog by allowing users to query their architecture through various tools.

  • Is there a cost associated with using the MCP Server?

The MCP Server is part of the EventCatalog Pro Edition, which may have associated costs.

  • Can I use the MCP Server with any IDE?

The MCP Server is designed to work with MCP-supported IDEs, but integration with other tools is possible using the LLMS.txt standard.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
event-catalog
Star
13
Language
TypeScript
License
View license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago