# quest-log-mcp

An MCP server for managing [quest-log](https://github.com/hooptiej/quest-log)'s ideas,
statuses, and mission log — so Claude (or any MCP client) can track and update projects
directly, without any of that data ever going through git/GitHub.

## Tools

| Tool | Description |
|---|---|
| `list_quests` | List quests, optionally filtered by status (idea/progress/blocked/done) |
| `add_idea` | Add a new idea/project/task to the idea board |
| `set_quest_status` | Update an existing quest's status by id or title match |
| `update_quest_notes` | Replace an existing quest's notes text by id or title match |
| `add_log_entry` | Append an entry to the mission log for a given day (default today) |
| `get_full_state` | Get the complete raw state |

## Configuration

Copy `.env.example` to `.env` and set:

- `QUEST_LOG_BASE_URL` — base URL of the quest-log deployment this talks to
- `QUEST_LOG_INSECURE=1` — only set if quest-log uses a self-signed cert you trust (its
  default deployment does). Leave unset otherwise.
- `PORT` — HTTP port to listen on (default `4243`)

## Running locally

```bash
npm install
npm run dev
```

## Running with Docker

```bash
docker compose up -d --build
```

## Connecting a client

Speaks MCP over streamable HTTP at `POST /mcp`. Point a client at `http://<host>:4243/mcp`.
`GET /health` is available for basic uptime checks.