Your Tasks

Your Rules

1 · Run it

docker run -d --name oxitick -p 15773:15773 -v ./data:/app/data oxisoft/oxitick:latest

2 · Environment variables (all optional)

3 · Or start with docker compose

services:
  oxitick:
    image: oxisoft/oxitick:latest
    ports:
      - "15773:15773"
    volumes:
      - ./data:/app/data
    environment:
      - ADMIN_USERNAME=admin
      - ADMIN_PASSWORD=change-me-min-8-chars
    restart: unless-stopped

4 · Data in a fixed host directory

Prefer your data at a known path on the host — easy to find, easy to back up? Bind-mount an absolute directory. The server runs as UID 1000, so grant it write access first.

services:
  oxitick:
    image: oxisoft/oxitick:latest
    ports:
      - "15773:15773"
    volumes:
      - /srv/oxitick/data:/app/data
    environment:
      - ADMIN_USERNAME=admin
      - ADMIN_PASSWORD=change-me-min-8-chars
    restart: unless-stopped

sudo mkdir -p /srv/oxitick/data
sudo chown -R 1000:1000 /srv/oxitick/data

Then open http://your-host:15773/admin, create user accounts, and point the app at your server under Settings → Sync Settings. Keep the /app/data mount — it holds your entire state (database, uploads, auth secret); running without it means losing everything when the container is recreated.

The Model Context Protocol is how assistants talk to tools. Our server runs on your own machine over stdio and connects to the OxiTick server you already run, so your token never leaves your computer and nothing new is exposed to the internet.

1 · Create a token

In the app: Settings → Accounts → your account → App tokens → New token. Choose what it may do — read, read and write, or also delete — enter your account password, and copy it. It is shown once, and you can revoke it at any time.

2 · Connect your assistant

One command finds the clients you have installed, checks the token actually works before writing anything, and asks permission before touching each config file.

uvx oxitick-mcp setup

Prefer to do it yourself? Add --print and it writes nothing, just tells you exactly what to put where.

Tested clients

Anything that speaks MCP over stdio works. ChatGPT does not: its connectors accept only remote servers reachable over HTTPS, which would mean putting your token on an internet-facing endpoint. We would rather not recommend that.

The limits live in the server

Every restriction above is enforced by the OxiTick server, not by the client. They hold whether an assistant goes through MCP or straight at the API. And any list you would rather an assistant never saw can be switched off for them: open the list and turn on "Hide from apps and AI assistants". It then answers "not found" everywhere and appears in no search, while staying completely available on your own devices.