obseed in Claude and ChatGPT

AI assistant connectors (MCP)

obseed now offers a remote MCP endpoint at https://app.obseed.me/mcp. Claude, ChatGPT and other MCP clients with OAuth support can connect to your obseed account, answer questions with your own data and propose entries that you confirm in obseed.

Connecting

• One URL, no API keys: your assistant registers itself, sends you to the obseed sign-in page and only receives a token after you approve. The token is bound to the obseed endpoint.
• Explicit consent: the consent screen names the client and the host your data goes to. You confirm that the provider processes your health data under its own terms before anything is shared.
• Setup help: step-by-step instructions for Claude, Claude Code and ChatGPT are on the AI assistants page.

What the assistant can read

• Your data: sleep, HRV, resting heart rate, body composition, workouts, summaries, insights and tags.
• Only your data: every tool works with the account that approved the connection.

What the assistant can log

• Log tags: “Tag last night: sauna, two beers” becomes tag entries, with an optional comment.
• Add details to workouts: note, label, perceived exertion, how you felt and motivation for an existing session.
• Nothing without your OK: the assistant proposes, you confirm in obseed with one tap. What you see is exactly what gets saved. The assistant cannot delete anything.

Control and privacy

• Settings → AI assistants: see every connected client and disconnect it. Disconnecting revokes that client’s tokens.
• Clear logs: obseed logs each call’s tool, account, client, inputs, outcome and duration, but not the health data it returns. Logs are deleted after 180 days.
• Untrusted text: free text such as workout names and tag notes is marked as untrusted data in tool results.