📖 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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago