MCP connectivity · Pilot

Your health history.
Your preferred AI agent.

Connect Micros Tracker to an AI agent through the Model Context Protocol (MCP). Bring your supplement intake, food logs, and lab measurements into the conversation you already use.

Set up your connection

Codex browser authentication and refresh have been verified. Other agent hosts require compatibility testing and client registration.

Read your history

Ask about recorded supplement intake, meals, nutrient snapshots, and lab measurements across dates.

Log from your conversation

Save user-authorized supplement intake, meals, and structured lab measurements with read/write permissions.

Stay in control

Choose permissions in the browser, check trial or paid access, and disconnect an agent at any time.

Connect your agent

  1. Register your agent client for the pilot

    Contact us with your agent application and its OAuth callback URL. Client registration is currently managed by Micros Tracker; entering the server URL alone may not be enough. Never send passwords or tokens.

    Request MCP setup

  2. Add the MCP server in your agent

    Use the HTTPS server URL below and the client configuration provided during setup. The server uses Streamable HTTP and OAuth with PKCE.

    https://microstracker.com/mcp

  3. Open the agent’s authorization link

    Sign in or create an account in the browser with email/password, Google, or Apple. Existing iOS Apple users can use the same Apple account. Review the requested permissions, approve, and return to your agent.

  4. Check access and start a conversation

    Ask your agent to check your account status. Reads remain available after trial expiry; new writes require active access and the appropriate permissions. Connecting does not start a trial or purchase a plan.

Questions about MCP

What can I ask my agent?

“Show my recorded magnesium intake last week.” “Log the meal I just described after confirming the portions.” “Compare my recorded lab values by collection date.” Missing records remain unknown; the connection does not establish medical causes or diagnoses.

Will I need to sign in throughout the day?

When you approve persistent access, your agent can refresh its connection for up to 30 days. Disconnecting revokes access; a new authorization is required when the connection expires.

Does every AI application support this?

No. Your host must support remote MCP and the configured OAuth client flow. Codex has been tested. Compatibility with Claude, Grok, and other hosts is not yet certified.

Your private records require authorization. You choose read and write scopes; agents must obtain your authorization before saving records. Manage connected agents.

For integrators: protected resource metadata · OAuth server metadata · LLM discovery guide.