Strata exposes tools through Model Context Protocol, or MCP, so a compatible assistant can work with your records. The connection links your signed-in account to the assistant you choose. Start with a read-only question before trying conversational logging.
Know what you are connecting
The Strata app remains the place where you can inspect your records. A connected assistant can request supported reads and writes through tools. A question may retrieve health information; a logging instruction may create or change a record.
Your assistant provider's terms and data policies apply to information it receives. Review those policies and the authorization screen before connecting. Connecting an assistant does not mean all of its possible actions are appropriate for every task.
Use the connection details inside Strata
Open AI Assistants in the web app and copy the MCP server URL shown there. In your assistant's current connector setup, add that URL and complete Strata's sign-in and authorization flow. Provider interfaces and account availability can change, so use the provider's current instructions for its side of setup.
Copy the endpoint from the app rather than reconstructing it from an old screenshot. The mockup here illustrates the flow without serving as a copyable configuration.
- Open Strata's AI Assistants page.
- Copy the server URL displayed in your account.
- Add it through your provider's supported MCP connection flow.
- Review authorization and finish sign-in.
Test with one existing record
Ask for a meal or sleep record whose date you already know. Check that the assistant retrieves the correct period and units, then compare its answer with the app. If it cannot access the tools, check the connection before repeating requests.
Next, try a deliberately narrow comparison, such as the recorded nights in one week. This confirms that you understand how the assistant presents missing data as well as populated results.
Review writes more carefully
A connection is not a reason to delegate every action. Name the specific entry and intended change when asking for a correction. Verify the saved result afterward.
If you stop using the connection, review the provider's connection-management controls and disconnect it there. Existing conversations may still contain information that was previously returned; removing a connection is separate from deleting conversation history.
An illustrative example
The first connection test
Alex asks, 'Show the lunch I recorded on October 7, including the description and portions.' After comparing it with Nutrition, Alex knows whether the connection is reaching the expected record before asking it to log a new meal.
Keep this in mind
Use current connection details, review access, and prove the connection with a small query you can verify.