laf-mcp-template

This is the starting point for an MCP server that connects your service to the LAF bot. The contract is just one page — mcp-contract.md — and this repository is a runnable minimal implementation of that contract, plus a pre-submission checker and CI.

Create your own repo with the Use this template button, and once you fill in just collectSignals(), the standard tool laf.watch is complete.

Getting started

bun install
bun start          # http://127.0.0.1:8765/mcp
bun run check      # 제출 전 검사 — 등록 화면과 같은 질문을 CI에서 미리

Remote server checks run with bun laf-mcp-check.ts <url> [--token <bearer>] [--json].

Related MCP server: wrg-mcp-server

Fill-in order

1. collectSignals() — only the things that are "critical if they stop." This is not telemetry; it's the on-call list. Threshold decisions (how many before warn) must be finalized on the server and emitted as status. Even if the backend dies, respond with a signal instead of a protocol error (contract §1.2).

2. Add free tools — one tool per task you want the bot to do, 10 tools or fewer recommended. Declare MCP standard annotations for each tool (contract §2). Tools without annotations are treated as maximum-risk (destructive) at registration, so the bot effectively can't use them. Don't build write tools from the start — run for a week with read-only tools first, then add only the ones that turn out to be needed. That's actually faster.

3. Pass the check — until bun run check reports FAIL 0. The included GitHub Actions workflow runs the same check on every push.

4. Deploy — to your own infrastructure. Code review, secret management, and availability are your responsibility; only the URL and Bearer token are passed to the platform.

5. Register — register the URL in the LAF admin screen, and the platform polls laf.watch periodically (no model, pure code) and turns only the appearance, disappearance, and transitions of signals into events. Free tools run in bot conversations according to their declared risk level — reads run quietly, while destructive, outbound, and money-related actions wait for human approval.

Don'ts

• Don't defer threshold decisions to the platform — status is finalized on the server.

• Don't surface backend failures as protocol errors — respond with signals.

• Don't omit annotations — everything is treated as destructive.

• Don't downgrade annotations after registration — it's treated as privilege escalation and triggers automatic suspension plus re-consent.

Files

MIT — LICENSE.