@eventcatalog/core 5.0.0-beta.9 → 5.0.1

package/dist/docs/development/studio/05-connect-your-agent.md

@@ -0,0 +1,102 @@
+---
+sidebar_position: 5
+keywords:
+- EventCatalog Studio
+- AI agents
+- MCP
+- MCP Apps
+sidebar_label: Connect your agent to a canvas
+title: Connect your agent to a canvas
+description: Bring Claude, ChatGPT, Cursor or another AI agent onto a canvas to design with you.
+---
+
+AI agents can join a canvas and work on it with you, live. An agent can add resources from your catalog, sketch new components, connect them, tidy the layout, comment and change the status.
+
+Agents join like a person does. Each one has its own pointer and name, and you see what it's doing ("Connecting InstalmentPlanApproved to Notification Service") as it works. Choose **Follow** on the "is working" banner to move your view with it.
+
+![Claude connecting an event to the Notification Service while two people are on the canvas](./img/studio-collaboration.png)
+
+## Before you start
+
+Agents connect through the [EventCatalog MCP server](/docs/development/ask-your-architecture/mcp-server/introduction), so your catalog must run with `output: 'server'`, including when you use `eventcatalog dev`.
+
+The MCP server is at `/docs/mcp`, for example `https://your-eventcatalog.com/docs/mcp`.
+
+## Connect with one prompt
+
+1. On the canvas, choose **Share**, then **Connect agent**. Or open the canvas menu and choose **Connect your AI agent**.
+2. Choose **Copy prompt**.
+3. Paste the prompt into your agent.
+
+The prompt tells the agent which canvas to join and how to connect to your catalog.
+
+![The Connect your AI agent dialog](./img/connect-agent.png)
+
+## Set up your client
+
+### Claude
+
+1. Open **Settings → Connectors** and choose **Add custom connector**.
+2. Name it `EventCatalog` and paste your MCP server URL.
+3. In a chat, turn the connector on and ask Claude to join your canvas.
+
+### Claude Code
+
+```bash
+claude mcp add --transport http eventcatalog https://your-eventcatalog.com/docs/mcp
+```
+
+Then ask Claude Code to join your canvas.
+
+### ChatGPT
+
+1. Open **Settings → Apps & Connectors**, turn on developer mode and create a connector with your MCP server URL.
+2. In a chat, add the connector and ask ChatGPT to join your canvas.
+
+### Cursor
+
+```json title=".cursor/mcp.json"
+{
+  "mcpServers": {
+    "eventcatalog": { "url": "https://your-eventcatalog.com/docs/mcp" }
+  }
+}
+```
+
+### VS Code
+
+Use Copilot's agent mode.
+
+```json title=".vscode/mcp.json"
+{
+  "servers": {
+    "eventcatalog": { "type": "http", "url": "https://your-eventcatalog.com/docs/mcp" }
+  }
+}
+```
+
+### Agents in your browser
+
+In the **Connect your AI agent** dialog, choose **This browser**, then **Turn on**. Agents in your browser, such as the MCP-B extension, can then use the open canvas through WebMCP.
+
+## The canvas inside your chat
+
+In clients that support [MCP Apps](/docs/development/ask-your-architecture/mcp-server/getting-started#interactive-diagrams-and-schemas), such as Claude and ChatGPT, the agent can open the canvas inside the conversation. You and the agent work on it there, and everyone with the canvas open in EventCatalog sees the same changes.
+
+## Things to ask
+
+**Design ideas together**
+
+- "Add a payments service that listens to OrderPlaced"
+- "How could we split the orders service?"
+- "Add retries and a dead letter queue to this"
+
+**Understand how it works**
+
+- "Put everything the Orders domain owns on the canvas"
+- "Walk me through what happens when a payment fails"
+- "Which services consume this event?"
+
+Agents work from your catalog, so the services and messages they add are the ones your teams document. They talk to you in the chat, and only comment on the canvas when you ask them to, for example to review it.
+
+See the [reference](/docs/development/studio/reference#mcp-tools) for the MCP tools agents use.

package/dist/docs/development/studio/06-run-studio-in-production.md

@@ -0,0 +1,54 @@
+---
+sidebar_position: 6
+keywords:
+- EventCatalog Studio
+- production
+- deployment
+sidebar_label: Run Studio in production
+title: Run Studio in production
+description: Turn on Studio for a deployed catalog.
+---
+
+Studio is on when you run `eventcatalog dev`. To use it in a deployed catalog, run your catalog in [server mode](/docs/development/deployment/build-ssr-mode) and turn Studio on. Studio isn't available in a static build.
+
+1. In `eventcatalog.config.js`, set `output` to `'server'` and `studio.enabled` to `true`:
+
+   ```js title="eventcatalog.config.js"
+   export default {
+     output: 'server',
+     studio: {
+       enabled: true,
+     },
+   };
+   ```
+
+2. [Set up persistent storage](/docs/development/studio/set-up-persistent-storage). Without it, canvases are lost when the server restarts.
+
+3. Build your catalog and serve it with `eventcatalog start`:
+
+   ```bash
+   npx eventcatalog build
+   npx eventcatalog start
+   ```
+
+## Behind a proxy or load balancer
+
+- **Forward WebSocket connections.** Live collaboration uses a WebSocket on the same port as your catalog.
+- **Trust your HTTPS host.** If your proxy serves the catalog over HTTPS, add your host to `security.allowedDomains`. Otherwise forms such as **New canvas** fail the origin check.
+
+  ```js title="eventcatalog.config.js"
+  export default {
+    output: 'server',
+    security: {
+      allowedDomains: [{ hostname: 'catalog.example.com', protocol: 'https' }],
+    },
+  };
+  ```
+
+## Only let signed-in people in
+
+Turn on [authentication](/docs/development/authentication/introduction). Only signed-in people can then open canvases.
+
+## Turn Studio off
+
+Set `studio.enabled` to `false`. This turns Studio off everywhere, including in `eventcatalog dev`.

package/dist/docs/development/studio/07-reference.md

@@ -0,0 +1,294 @@
+---
+sidebar_position: 7
+keywords:
+- EventCatalog Studio
+- reference
+sidebar_label: Reference
+title: Studio reference
+description: Configuration, canvas controls, components, connection labels, MCP tools, keyboard shortcuts and limits for EventCatalog Studio.
+---
+
+Everything about Studio and its canvases in one place.
+
+## Configuration {#configuration}
+
+### `studio`
+
+| Option | Type | Default | Description |
+|---|---|---|---|
+| `studio.enabled` | `boolean` | `false` | Turns Studio on in production. Studio is on in `eventcatalog dev` unless this is `false`. `false` turns it off everywhere. |
+
+### `storage`
+
+| Option | Type | Default | Description |
+|---|---|---|---|
+| `storage.type` | `'memory'` \| `'sqlite'` | `'memory'` | `'memory'` keeps canvases while the server runs. `'sqlite'` keeps them in a database file. |
+| `storage.path` | `string` | `'.eventcatalog/eventcatalog.db'` | The SQLite database file, relative to your catalog. |
+
+SQLite storage needs Node.js 22.13 or later.
+
+### Related options
+
+| Option | Why it matters for Studio |
+|---|---|
+| `output` | Must be `'server'` for Studio in production, and for agents to connect through the MCP server. |
+| `auth.enabled` | With [authentication](/docs/development/authentication/introduction) on, only signed-in people can open canvases. |
+| `mcp.enabled` | Agents connect through the MCP server. Setting it to `false` stops agents connecting. |
+| `security.allowedDomains` | Needed when a proxy serves your catalog over HTTPS. |
+
+### When Studio is on
+
+| Command | `studio.enabled` not set | `true` | `false` |
+|---|---|---|---|
+| `eventcatalog dev` | On | On | Off |
+| `eventcatalog start` (`output: 'server'`) | Off | On | Off |
+| Static build (`output: 'static'`) | Off | Off | Off |
+
+### Example
+
+```js title="eventcatalog.config.js"
+export default {
+  output: 'server',
+  studio: {
+    enabled: true,
+  },
+  storage: {
+    type: 'sqlite',
+    path: '/data/eventcatalog.db',
+  },
+};
+```
+
+See the [full configuration reference](/docs/api/config) for every EventCatalog option.
+
+## Canvas {#canvas}
+
+### Toolbar
+
+| Button | Shortcut | What it does |
+|---|---|---|
+| Lock | | Locks the canvas, so it can be looked at but not changed |
+| Select | <kbd>V</kbd> | Select and move nodes |
+| Hand | <kbd>H</kbd> | Drag to move around |
+| L1 / L2 / L3 | <kbd>1</kbd> <kbd>2</kbd> <kbd>3</kbd> | Change the [level](#levels) |
+| Sticky note | <kbd>N</kbd> | Click where the note goes |
+| Text | <kbd>T</kbd> | Click anywhere and type |
+| Comment | <kbd>C</kbd> | Click a node, or a spot, to comment |
+| Hotspot | <kbd>A</kbd> | Click a node, or a spot, to flag a risk |
+
+The controls at the bottom left zoom, undo and redo, fit the view (<kbd>⇧</kbd> <kbd>1</kbd>), reorder the diagram, and list comments and hotspots.
+
+### Levels
+
+| Level | Shows |
+|---|---|
+| **L1** | Domains, systems and their relationships |
+| **L2** | Services and data stores |
+| **L3** | Everything, including messages and channels |
+
+L1 is unavailable until the canvas has a domain or system.
+
+### Canvas menu
+
+The three dots next to the canvas title.
+
+![The canvas menu](./img/canvas-menu.png)
+
+| Item | Shortcut |
+|---|---|
+| Open… | <kbd>⌘</kbd> <kbd>O</kbd> |
+| Save to file… | <kbd>⌘</kbd> <kbd>S</kbd> |
+| Export image… | <kbd>⌘</kbd> <kbd>⇧</kbd> <kbd>E</kbd> |
+| Live collaboration… | |
+| Connect your AI agent… | |
+| Help | <kbd>?</kbd> |
+| Rename canvas | |
+| Copy link | |
+| New canvas | |
+| Delete canvas | |
+
+The bottom of the menu shows the connection status, for example **Connected**.
+
+### Right-click menus
+
+| On | Items |
+|---|---|
+| A node | Add comment, Add hotspot, Add a note, Edit details, Copy, Duplicate, Delete |
+| The canvas | Add comment, Add hotspot, Add a sticky note, Paste here, Reorder diagram |
+
+### Statuses
+
+| Status | Meaning |
+|---|---|
+| **Draft** | Being worked on. Every canvas starts as a draft. |
+| **Proposed** | Ready for review |
+| **Accepted** | The agreed design |
+| **Rejected** | Decided against, kept for the record |
+
+- Each status change can have a note. The status menu shows the history, with who changed it, when and the note.
+- Changing the nodes or connections on an accepted or rejected canvas makes it a draft again.
+
+### Hotspots
+
+| Field | Values |
+|---|---|
+| Severity | **Critical** (red), **Warning** (amber) or **Info** (blue) |
+| Title | Up to 120 characters, for example "Single point of failure" |
+| Description | Optional. Why it matters, and what to do about it |
+
+- A hotspot is on a node, and moves with it, or on a spot on the canvas.
+- The **Hotspots** list shows the most severe first.
+- At L1 and L2, hotspots inside a domain or system are shown on that domain or system.
+
+### Studio page
+
+The Studio page lists canvases with their status, contents, open comments, who created them, and when they were last updated. Filter by name or status. Each canvas's menu has **Make a copy** and **Delete**.
+
+### Limits
+
+| Limit | Value |
+|---|---|
+| Canvas title | 200 characters |
+| Your name | 60 characters |
+| `.eventcatalog` file | 2 MB |
+
+## Components and connections {#components-and-connections}
+
+### Components
+
+New components start at version `0.0.1`.
+
+| Group | Component | Description |
+|---|---|---|
+| Boundaries | Domain | A business area, e.g. Sales |
+| | System | Services doing one job |
+| Services | Service | An API, worker or function |
+| | View | A screen or app people use |
+| | External System | A third party you use |
+| | Agent | An AI agent at work |
+| Messages | Event | Something that happened |
+| | Command | A request to do something |
+| | Query | A request for data |
+| | Channel | A topic, queue or bus |
+| Data | Database | Tables, e.g. PostgreSQL |
+| | Cache | Fast data, e.g. Redis |
+| | Search index | Search, e.g. Elasticsearch |
+| | Object store | Files and blobs, e.g. S3 |
+| | Entity | Part of the domain model |
+| People | Actor | Someone who uses it |
+| | Team | Who owns what |
+
+Sticky notes and text are added from the toolbar.
+
+### Catalog resources
+
+You can add these resources from your catalog: domains, systems, services, events, commands, queries, channels and data stores. They are added at their latest version, with their name, version and summary from your catalog.
+
+### Connection labels
+
+When you connect two nodes, Studio labels the connection with EventCatalog's wording:
+
+| From | To | Label |
+|---|---|---|
+| Service, agent, actor, external system or view | Event | publishes event |
+| Service, agent, actor, external system or view | Command | invokes |
+| Service, agent, actor, external system or view | Query | requests |
+| Event | Anything but a message or channel | subscribed by |
+| Command or query | Anything but a message or channel | accepts |
+| Message | Message | triggers |
+| Message | Channel | sent to |
+| Channel | Anything | routes to |
+| Anything else | Channel | publishes to |
+| Anything | Data store | writes to |
+| Data store | Anything | read by |
+| Actor | Anything | uses |
+| Anything | View | serves |
+| Anything | External system | calls |
+| Anything | Actor | notifies |
+| Team | Anything | owns |
+| Entity | Entity | references |
+| Message | Entity | carries |
+| Anything else | Entity | manages |
+
+Agents can set their own labels through the [MCP tools](#mcp-tools).
+
+## MCP tools {#mcp-tools}
+
+When Studio is on, the [EventCatalog MCP server](/docs/development/ask-your-architecture/mcp-server/introduction) has these tools for canvases. Unlike the other MCP tools, they change your canvases.
+
+| Tool | What it does |
+|---|---|
+| `openCanvas` | Shows a canvas in the chat, in clients that support MCP Apps |
+| `listCanvases` | Lists canvases and who is on each one |
+| `createCanvas` | Creates a canvas and returns its link |
+| `getCanvas` | Reads a canvas: its nodes, connections, comments and who is on it |
+| `addToCanvas` | Adds catalog resources or new components, and connects them |
+| `updateCanvasNode` | Renames, describes, versions or moves a node |
+| `connectCanvasNodes` | Connects nodes |
+| `removeFromCanvas` | Removes nodes or connections |
+| `layoutCanvas` | Lays out the whole canvas |
+| `setCanvasStatus` | Sets the status to draft, proposed, accepted or rejected, with a note |
+| `commentOnCanvas` | Starts a comment thread on a node or a spot |
+| `replyToCanvasComment` | Replies to a thread |
+| `resolveCanvasComment` | Resolves or reopens a thread |
+
+Every tool takes an optional `agentName`, the name people on the canvas see. It defaults to the name of the client, for example Claude, Claude Code, ChatGPT or Cursor.
+
+### How agents appear
+
+- An agent has its own pointer and name on the canvas.
+- Its changes appear one step at a time, with what it is doing, for example "Connecting InstalmentPlanApproved to Notification Service".
+- A banner shows when an agent is working. Choose **Follow** to move your view with it.
+
+### Browser tools (WebMCP)
+
+When WebMCP is turned on in the **Connect your AI agent** dialog, the open canvas offers agents in the browser these tools: `get_canvas`, `search_catalog`, `add_to_canvas`, `update_node`, `connect_nodes`, `remove_from_canvas`, `layout_canvas`, `set_canvas_status`, `add_comment`, `reply_to_comment`, `resolve_comment` and `show_nodes`.
+
+## Keyboard shortcuts {#keyboard-shortcuts}
+
+Press <kbd>?</kbd> on a canvas to see these shortcuts. On Windows and Linux, use <kbd>Ctrl</kbd> instead of <kbd>⌘</kbd>.
+
+![The keyboard shortcuts dialog](./img/keyboard-shortcuts.png)
+
+### Tools
+
+| Action | Shortcut |
+|---|---|
+| Select | <kbd>V</kbd> |
+| Hand (move around) | <kbd>H</kbd> |
+| Sticky note | <kbd>N</kbd> |
+| Text | <kbd>T</kbd> |
+| Comment | <kbd>C</kbd> |
+| Hotspot | <kbd>A</kbd> |
+| Level 1 / 2 / 3 | <kbd>1</kbd> <kbd>2</kbd> <kbd>3</kbd> |
+| Back to selecting | <kbd>Esc</kbd> |
+
+### Canvas
+
+| Action | Shortcut |
+|---|---|
+| Select everything | <kbd>⌘</kbd> <kbd>A</kbd> |
+| Select several | <kbd>⇧</kbd> + click |
+| Delete what's selected | <kbd>Delete</kbd> |
+| Duplicate | <kbd>⌘</kbd> <kbd>D</kbd> |
+| Copy / paste | <kbd>⌘</kbd> <kbd>C</kbd> / <kbd>⌘</kbd> <kbd>V</kbd> |
+| Undo / redo | <kbd>⌘</kbd> <kbd>Z</kbd> / <kbd>⌘</kbd> <kbd>⇧</kbd> <kbd>Z</kbd> |
+| Move around | Scroll |
+| Zoom | <kbd>⌘</kbd> + scroll |
+| Fit view | <kbd>⇧</kbd> <kbd>1</kbd> |
+
+### Notes and text
+
+| Action | Shortcut |
+|---|---|
+| Write on one | Double-click |
+| Finish writing | <kbd>Esc</kbd> |
+
+### Files
+
+| Action | Shortcut |
+|---|---|
+| Open a file | <kbd>⌘</kbd> <kbd>O</kbd> |
+| Save to file | <kbd>⌘</kbd> <kbd>S</kbd> |
+| Export image | <kbd>⌘</kbd> <kbd>⇧</kbd> <kbd>E</kbd> |
+| Help | <kbd>?</kbd> |

package/dist/docs/development/studio/_category_.json

@@ -0,0 +1,12 @@
+{
+  "label": "Studio",
+  "position": 4.5,
+  "collapsible": true,
+  "collapsed": false,
+  "link": {
+    "type": "generated-index",
+    "slug": "development/studio",
+    "title": "EventCatalog Studio",
+    "description": "Design changes to your architecture on live canvases, with your team and AI agents."
+  }
+}