Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›MCP surface·41 in this wave

Approve: MCP surfaceTo do · blocker 13 production secrets overdue for rotation — the gate cannot be green until this is resolvedTo do · blocker Deploy step 2 — verify/rotate production MCP Worker secretsTo do Deploy step 4 — fix the stale "NOT DEPLOYED" banner and deploy docsDone Add action.* and bluetooth.* op groups to the MCP catalogDone Build real handlers for group.* (9 ops)Done Build real handlers for family.* (7 ops)Done Build settings.* MCP tools including custom domain managementTo do Verify/build the Connected Apps management UI for MCP OAuth clientsTo do Add rate limiting, quota, and cost controls to the hosted MCP serverDone Honesty check — reconcile investor deck MCP claims against what shipsTo do Verify "everything a human can do, an agent can do over MCP" end to endTo do staging-api is a day behind main — and writes to the production SupabaseTo do MCP GAP INVENTORY — every unwired op, with the decision attached to eachDone Demo account for screenshots + QA — seeder is live, shape is frozenTo do Build the full medialink.* MCP tool set (3 ops)To do Build the payment.* connector MCP tool set (3 ops)To do Build the full webhook.* MCP tool set (4 ops)Done Build zap.* MCP tools or explicitly cut Zapier from v1.0 MCP scopeTo do Build link.schedule.repoint, link.compound, wizard.suggest or cut themTo do Deploy step 1 — verify DB migration + RLS on OAuth tablesTo do Deploy step 3 — confirm CF route/DNS for mcp.tactile.to is production-gradeTo do Deploy step 5 — formalize the MCP smoke testTo do Build nfc.lock and nfc.unlock MCP toolsTo do Build contact.vcard.export and contact.delete MCP toolsTo do Build linkhub.create and linkhub.delete MCP toolsDone Build videoaudio.create and videoaudio.replace MCP toolsTo do Build document.create and document.replace MCP toolsTo do Build the full social.* MCP tool set (6 ops)To do Build the full paylink.* MCP tool set (4 ops)Done Build wifi.edit MCP toolTo do Build the full form.* MCP tool set (7 ops)Done Build the analytics automation layer MCP tools (6 ops)To do Wire inbox.list and inbox.mcp_approval to real handlersDone Add architecture test guarding against a second tool-handler implementationTo do Publish a public MCP tool manifest / discovery docsTo do Webhook signing secret: add the one surface that can reveal itDone A Website destination's URL cannot be edited through the agent surface at allDone SPEC → backend: webhook secret reveal/rotate endpoints + secret_fingerprint on the listDone NEEDS MATTHEW: decide whether resolve_trigger_destination keeps anon EXECUTEBlocked 5 proposal-only MCP ops are advertised with no task row building themTo do

Wave

MCP surface

Thesis pillar 3 — "Agentic AI + MCP." The investor deck claims first-in-category MCP-native. Audit (2026-07-26) found the hosted server IS live at mcp.tactile.to with real OAuth production traffic (14 clients, 11 tokens) — but the code's own deploy banner still says "NOT DEPLOYED" (stale), and tool coverage is genuinely incomplete: roughly half the 147-op catalog are proposer stubs that never mutate state, and 2 of 14 destination types (Action, Bluetooth) have zero MCP presence at all. Not cuttable: this is a stated structural moat.

TacTile › Launch TacTile › MCP surface

14/41 done27 open2 open blockers

Selected taskclear

5 proposal-only MCP ops are advertised with no task row building them

To doOwner · met_34d9afd5

Found 2026-08-12 by deriving the MCP inventory (#371). Decide build-or-cut for each; they are advertised to every connected MCP client today.

No dependencies in this wave — nothing gates it, and nothing waits on it.

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**5 proposal-only MCP ops are advertised with no task row building them** · to do

Found 2026-08-12 by deriving the MCP inventory (#371). Decide build-or-cut for each; they are advertised to every connected MCP client today.

Where it sits: TacTile › Launch TacTile › MCP surface

## The brief on file

Filed 2026-08-12 by the round-18 backend session. This is a DECISION row, not an implementation row.

Deriving the MCP tool inventory from the registry (PR #371, docs/mcp/TOOL-INVENTORY.md) surfaced that 46 of the 198 registered tools are proposal-only — advertised to clients, no wired handler, they THROW when resolved. 41 map to one of the 11 open "Build X MCP tools" rows in this wave. FIVE map to nothing:

  family.merge
  family.tag_by_rule
  link.compound
  link.schedule.repoint
  wizard.suggest

Nothing in the plan builds them and every connected MCP client is told they exist.

DECIDE, per op: build it (file a row in this wave, matching the shape of t_e17c3942 / t_a85b9b84), or cut it from packages/mcp-server/src/ops/catalog.ts. Either resolves it; leaving them is the only wrong answer, because the inventory now records them as unclaimed on every run and that will read as accepted rather than unnoticed.

RELATED AND SEPARATE — the decision that is still yours: whether the hosted MCP Worker should hide proposal-only tools or keep listing them and failing loudly. It has been framed as "198 -> 149" everywhere. 149 is not a number this registry produces; the real figure is 152, and CATALOG_TOOLS(152) and CUSTOMER_TOOLS(152) are the same SIZE but NOT the same SET — CUSTOMER is 106 wired catalog ops plus 46 legacy tools. Read docs/mcp/TOOL-INVENTORY.md before deciding; it regenerates from the registry so it cannot go stale the way 149 did.

Two naming corrections for the row list in this wave: t_fe9ef9e4 says `payment.*` but the proposal-only ops are `payment_connector.*` (3) — the plain `payment.*` names are real wired CRUD in tools/payment.ts and must stay that way. t_5a80f43e's "zap.* or cut" is 4 ops: zap.connect, zap.disconnect, zap.select, zap.test.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

MCP surface

5 proposal-only MCP ops are advertised with no task row building them