MCP server for EventCatalog
MCP server for EventCatalog
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| find_resources | Find resources that are available in EventCatalog including services, domains, events, commands, queries, flows, entities, channels, teams, users, and docs |
| find_resource | Get more information about a service, domain, event, command, query, flow, entity, or channel in EventCatalog using its id and version |
| find_owners | Find owners (teams or users) for a domain, service, message, event, command, query, flow, or entity in EventCatalog |
| find_producers_and_consumers | Get the producers (sends) and consumers (receives) for services in EventCatalog |
| get_schema | Returns the schema for a service (e.g., OpenAPI, AsyncAPI, GraphQL), event, command, or query in EventCatalog |
| review_schema_changes | Reviews schema changes for breaking changes and suggests fixes |
| explain_ubiquitous_language_terms | Explain ubiquitous language terms for a given domain |
| create_flow | Create a new flow in EventCatalog given a description of the business workflow |
| eventstorm_to_eventcatalog | Turn a photo of an EventStorm session into an EventCatalog |
| create_eventcatalog | Create a new EventCatalog project from scratch |
{
"mcpServers": {
"eventcatalog": {
"command": "npx",
"args": ["-y", "tsx /PATH_TO_YOUR_REPO/src/index.ts", "https://demo.eventcatalog.dev", "ABCD-1234-5678-9012-3456-7890"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LICENSE_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace β read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
MCP server for MTS Exolve β SMS, calls, recordings, Viber messaging (Russia)
Model-agnostic computer-use MCP: screenshot, safety-gated actions, Windows UIA targeting.
Validate SMS-capable phone numbers -- mobile vs landline detection, carrier type, E.164 format, SMS readiness. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Give AI agents access to ClawdCall's agent-facing phone execution API through the Model Context Protocol.