• MCP server runs on lightberry server
• lightberry device functions as a REST API endpoint
  • this means there is slightly more overhead on the client device, as it needs to run the server infrastructure. but it would need to do that anyways if it ran the mcp server locally.
• MCP server routes tool calls to the correct device id. we need to add an endpoint to our api which fetches the correct ip from tailscale.
  • This requires a llittle bit of tailscale setup. We can do it publically for now to speed it up, should be easy to retrofit later.