start-server
/start-server
Start or stop a local EventSourcingDB instance in development mode using Docker, with temporary data storage, plain HTTP, the built-in web UI, and a simple API token. Use when the user wants to spin up a throwaway EventSourcingDB for local development or testing, or wants to stop it again.
- Author
- thenativeweb ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 02.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 4
No signals detected. Repository changed on 02.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Start or stop a local EventSourcingDB instance in development mode using Docker, with temporary data storage, plain HTTP, the built-in web UI, and a simple API token. Use when the user wants to spin up a throwaway EventSourcingDB for local development or testing, or wants to stop it again.
Original author description
Start or stop a local EventSourcingDB instance in development mode using Docker, with temporary data storage, plain HTTP, the built-in web UI, and a simple API token. Use when the user wants to spin up a throwaway EventSourcingDB for local development or testing, or wants to stop it again.
How it works
- Defaults
- Preflight
- Start
- Verify
- Report to the User
- Stop
SKILL.md preview
---
name: start-server
description: Start or stop a local EventSourcingDB instance in development mode using Docker, with temporary data storage, plain HTTP, the built-in web UI, and a simple API token. Use when the user wants to spin up a throwaway EventSourcingDB for local development or testing, or wants to stop it again.
allowed-tools: Bash, Read, AskUserQuestion
---
# Start Server (Development Mode)
Run a local EventSourcingDB instance for development and testing via Docker. The instance uses:
- Temporary data storage (`--data-directory-temporary`) – all data is lost when the container stops.
- Plain HTTP instead of HTTPS (`--http-enabled --https-enabled=false`).
- The built-in web UI (`--with-ui`).
- A simple API token (`secret`).
This setup is for development only. Never use it in production.
## Defaults
- Container name: `eventsourcingdb-dev`
- Port: `3000`
- API token: `secret`
- Image: `thenativeweb/eventsourcingdb:latest`
If the user asks for a different port, token, or image version, use their values instead.
## Preflight
Check that Docker is running, and whether a dev instance already exists or the port is taken:
```bash
docker info > /dev/null 2>&1 && echo "Docker: running" || echo "Docker: NOT running"
docker ps --all --filter "name=eventsourcingdb-dev" --format "{{.Names}} ({{.Status}})"
lsof -nP -iTCP:3000 -sTCP:LISTEN || echo "Port 3000 is free"
```
- If Docker is not running, ask the user to start Docker first, then stop.
- If a container named `eventsourcingdb-dev` is already running, do not start a second one. Inform the user that the instance is already available and report the connection details (see below).
- If the port is taken by another process, use AskUserQuestion to ask the user for an alternative port.
## Start
```bash
docker run -d --rm --name eventsourcingdb-dev -p 3000:3000 \
thenativeweb/eventsourcingdb:latest run \
--api-token=secret \
--data-directory-temporary \
--http-enabled \
--https-enabled=false \
--with-ui
```
When using a custom port, only change the host side of the mapping (e.g., `-p 3001:3000`); the container-internal HTTP port stays `3000`.
## Verify
Wait briefly, then ping the instance:
```bash
sleep 2
curl -s -i "http://localhost:3000/api/v1/ping"
```
Check that the response contains HTTP status `200 OK` and the `Server` header starts with `EventSourcingDB/`. If the ping fails, inspect the logs with `docker logs eventsourcingdb-dev` and report the problem.
## Report to the User
After a successful start, report:
- API base URL: `http://localhost:3000`
- Web UI: `http://localhost:3000`
- API token: `secret`
- Data is stored in a temporary directory and is deleted when the container stops.
Suggest exporting the environment variables so the other esdb skills pick up the instance automatically:
```bash
export ESDB_URL="http://localhost:3000"
export ESDB_API_TOKEN="secret"
```
## Stop
When the user wants to stop the instance:
```bash
docker stop eventsourcingdb-dev
```
Since the container was started with `--rm` and `--data-directory-temporary`, the container and all stored data are removed. Remind the user of this before stopping.
Versions
The database has no other skills named start-server.
Database snapshot: 13.11.2026 · package version 30d58152e1e1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100run-eventql-query
Run an EventQL query against an EventSourcingDB instance. Use when the user wants to query, filter, aggregate, or analyze events using the EventQL query language. - 100write-events
Write events to an EventSourcingDB instance. Use when the user wants to store, append, or publish events, optionally with preconditions such as optimistic locking or subject constraints. - 100observability
Start, stop, or check status of the Side Quest observability event server. Use when asked to start the server, stop the server, check server status, or manage the observability dashboard lifecycle. - 90docker-dev
Assistance with Local Development using Docker (Compose, DevContainers). Use when: docker, compose, local dev, devcontainer, dev environment, containerize, dockerization. - 90openrag_dev_stack
Start, monitor, restart, or stop the local OpenRAG dev stack (Docker infra + host backend + host frontend). Use when the user says "start the dev stack", "run the app locally", "restart the backend/frontend", "factory-reset", "is the stack up?", or asks to bring services up/down… - 95engine-manage
Manage the Kurtosis engine server. Start, stop, restart the engine, check status, and view engine logs. Covers both Docker and Kubernetes engine backends. Use when the engine won't start, needs restarting, or you need to check engine health.