부활절을 위한 기술: 클로드에게 연설하도록 가르치기 EventSourcingDB

A Skill for Easter: Teaching Claude to Speak EventSourcingDB¶ Two weeks ago, we introduced the MCP Server 1.0 for EventSourcingDB, connecting AI agents to your event store through the Model Context Protocol. It showed what becomes possible when LLMs can query events, inspect subjects, and run EventQL in natural language. But setting up a Docker container and configuring an MCP client is not always what you want when you just need to quickly interact with your database. Sometimes you want something lighter. As a small Easter gift, we are releasing a Claude Code Plugin for EventSourcingDB. It is a set of Skills that teach Claude how to use the entire EventSourcingDB API. No SDK installation, no Docker container, no MCP configuration. You install the plugin, and start talking to your event store. Think of it as the lightest possible bridge between natural language and your events. What Claude Code Plugins and Skills Are¶ Claude Code is Anthropic's CLI tool for working with Claude directly in the terminal. It can read files, run commands, write code, and reason about your project. Plugins extend what Claude Code can do by bundling one or more Skills. A Skill is a Markdown file that describes a specialized workflow step by step, including which tools to use, what API calls to make, and how to handle responses. When you invoke a Skill, Claude reads the instructions and follows them, much like an experienced colleague following a well-written runbook. You can think of Skills as checklists written by a domain expert. The Markdown file does not contain executable code. It contains knowledge: which endpoints exist, what parameters they expect, what the responses look like, and what conventions to follow. Claude brings the reasoning, and the Skill brings the domain expertise. Plugins are distributed through marketplaces, making installation as simple as a single command. For more details on how Plugins and Skills work, the Claude Code documentation covers the full specification. What the Plugin Does¶ The EventSourcingDB Plugin turns Claude into a fully capable API client for your event store. Instead of a single monolithic Skill, the plugin provides one focused Skill per API endpoint: /esdb:ping /esdb:verify-api-token /esdb:write-events /esdb:read-events /esdb:observe-events /esdb:read-subjects /esdb:read-event-type /esdb:read-event-types /esdb:run-eventql-query /esdb:register-event-schema You can invoke them explicitly, or simply describe what you want and let Claude pick the right one automatically. There is no configuration wizard, no project scaffolding, no dependency installation. The plugin goes from zero to connected in a single command. The plugin covers the same operations as the Client SDKs. You can write events with optional preconditions, read events for any subject with filtering and ordering, observe events in real time with automatic timeout handling, browse subjects, inspect event types, register JSON Schemas for validation, and run EventQL queries. Everything the HTTP API supports, the plugin supports. Under the hood, the Skills use only curl and grep , so there is nothing to install. Claude assembles the requests, parses the responses, filters out noise from streaming connections, and handles timeouts. You never have to think about the wire protocol. The difference between the plugin and writing curl commands yourself is not just convenience. It is the layer of reasoning that Claude adds on top. When you say "show me what happened to this order last Tuesday," Claude figures out which Skill to invoke, what filters to apply, and how to present the result in a way that answers your question. You stay in the domain language, and the plugin handles the translation. How does this compare to the MCP Server? The MCP Server is the right choice when you want a persistent, always-available connection between your LLM and EventSourcingDB, especially in setups where multiple tools and agents collaborate. It runs as a Docker container, speaks the Model Context Protocol, and works with any MCP-compatible client. The plugin is for those moments when you want to quickly explore your event store from the terminal without spinning up any infrastructure. Think of the MCP Server as the production integration and the plugin as the developer's scratchpad. Different tools for different situations. Setting It Up¶ Getting started takes less than a minute. Step 1: Add the thenativeweb plugin marketplace to Claude Code: Step 2: Install the EventSourcingDB plugin: Step 3: Tell Claude how to reach your database. The plugin reads two environment variables: If ESDB_URL is not set, the plugin defaults to http://localhost:3000 . If ESDB_API_TOKEN is not set, Claude will ask you for it when a Skill runs. Step 4: Open Claude Code in your terminal and type /esdb:ping to verify the connection. That is the entire setup. A Library in Five Minutes¶ To see what working with the plugin feels like, let us walk through a small example. Imagine