t4l-server 0.1.2

Self-hosted REST and MCP server for T4L Trainer agent workflows.

T4L Server

Self-hosted REST and MCP server for exchanging T4L Trainer JSON artifacts between the iPhone app and a coaching agent.

The phone remains the source of truth for accepted training state. The server stores synced context and pending agent results in SQLite so local agents, home-server agents, and private VPS agents can work through the same protocol.

Install

pipx install t4l-server
t4l-server serve --data-dir ~/T4LServerData

The command prints the server URL, MCP URL, and API key. Enter the server URL and API key in the T4L Trainer Settings screen.

Agent setup

Agents should read the public instruction repo first:

https://github.com/BigSlikTobi/t4l-agent-instructions

Those instructions explain how to start or verify this server, connect through MCP, wait for fresh phone context, and write app-consumed results safely.

Compatibility

The old command remains available for one transition cycle:

t4l-bridge serve --dir ~/CodexFitnessExchange

New setups should use t4l-server serve --data-dir ~/T4LServerData.

Safety model

• REST, MCP, and compatibility file endpoints require the API key.
• JSON artifacts are stored in t4l.sqlite.
• Image blobs are stored under blobs/.
• Only known exchange files and meal_images/ are accessible through compatibility endpoints.
• Path traversal and arbitrary file access are rejected.

Development

python -m venv .venv
. .venv/bin/activate
python -m pip install -e ".[dev]"
ruff format --check .
ruff check .
mypy
pytest
python -m build
twine check dist/*