tinyclaw

TinyClaw is an edge fact node runtime for turning raw device signals into stable, observable business facts.

The current first-class profile is occupancy-camera-v1: a camera-driven occupancy node that detects people, applies debounce and cooldown, models device health, and exposes the result over MCP.

TinyClaw is not just a camera wrapper and not just an MCP adapter.

It sits between the physical edge world and northbound protocol consumers:

• Southbound: camera frames, detector outputs, device timing, runtime health
• Middle layer: semantic convergence, state transitions, heartbeat, recent events
• Northbound: MCP tools, resources, notifications, stdio, and streamable HTTP

In short:

• MCP is the northbound protocol
• TinyClaw is the semantic runtime that decides what facts are worth publishing

Current default profile:

• occupancy-camera-v1

Current published facts:

• occupancy.changed
• device.heartbeat
• device.health_changed

Current MCP surface:

• Tools:
• tinyclaw.get_occupancy_status
• tinyclaw.capture_frame
• tinyclaw.get_config
• tinyclaw.get_device_health
• tinyclaw.set_config
• tinyclaw.reset_state
• Resources:
• tinyclaw://scene/{scene_id}/state
• tinyclaw://scene/{scene_id}/stats
• tinyclaw://scene/{scene_id}/events/recent
• tinyclaw://scene/{scene_id}/health
• Notifications:
• occupancy.changed
• device.heartbeat
• device.health_changed

Compatibility:

• tinyclaw.get_occupancy is still accepted as an alias for

tinyclaw.get_occupancy_status

TinyClaw V0.3 is structured in five layers:

1. Input Plugin

Brings raw world signals into the node. The current concrete implementation is a camera frame source.

1. Semantic Profile

Owns profile-specific convergence. For occupancy-camera-v1, that includes detection-to-candidate translation, debounce, cooldown, transition generation, and profile sna