📖 EventCatalog - MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is EventCatalog - MCP Server?

EventCatalog - MCP Server is an open-source tool designed to enhance the documentation and querying of event-driven architectures by integrating with various MCP clients.

how to use EventCatalog - MCP Server?

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

key features of EventCatalog - MCP Server?

  • Connects to multiple MCP clients (e.g., Claude, Cursor, Windsurf)
  • Local deployment with a single command
  • Queries about domains, services, messages, and schemas
  • Supports OpenAPI and AsyncAPI specifications
  • Provides schemas for events, queries, commands, and services

use cases of EventCatalog - MCP Server?

  1. Developers can document and query their event-driven architectures.
  2. Stakeholders can ask questions about the architecture using their preferred tools.
  3. Integration with various IDEs to enhance development workflows.

FAQ from EventCatalog - MCP Server?

  • Can I use EventCatalog with any MCP client?

Yes! EventCatalog supports multiple MCP clients and can be integrated with any that follow the MCP protocol.

  • Is there a cost associated with using EventCatalog - MCP Server?

No, it is an open-source tool and free to use.

  • How do I contribute to the project?

You can contribute by cloning the repository, installing dependencies, and submitting pull requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
View license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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