davidmosiah Fitbit — skill or MCP
Same binary either way. Do not duplicate the API client.
Choose a surface
MCP — tools appear natively after stdio/HTTP config:
{ "mcpServers": { "fitbit": { "command": "npx", "args": ["-y", "fitbit-mcp-unofficial"] } } }
Do not put mutation flags in that snippet.
Skill / CLI — no MCP client required. Same tools:
npx -y fitbit-mcp-unofficial call fitbit_connection_status --json '{}'
If MCP tools named fitbit_* are already available, use them. Do not also shell out.
Loop
- Call
fitbit_connection_status(ordoctor --jsonwhen that exists). - Use read tools as asked.
- Stop on
USER_ACTION_REQUIRED. Do not invent env flags. Do not enable mutations from this skill.
Never
- Paste tokens into git, chat logs, or the prompt
- Copy a mutations-enabled assignment into config