📖 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
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.

3 hours ago