Connect VitalTrends to Gemini, Perplexity, Mistral, Copilot Studio, Poke and other assistants
Many AI assistants now accept a custom remote MCP server. This page covers the ones that do, with steps taken from each vendor's documentation, and says plainly where an assistant can't connect yet.
Server URL: https://mcp.vitaltrends.net/mcp (Streamable HTTP). A legacy SSE endpoint is also served at https://mcp.vitaltrends.net/sse, but most of the assistants below only accept Streamable HTTP.
Last checked: 21 November 2026. None of the assistants on this page has been tested end to end by VitalTrends yet. For the assistants we have verified, see Claude, ChatGPT, Codex and Grok.
Requirements
- An active VitalTrends subscription and at least one synced data source.
- Your personal API key from Settings → Developer.
- An account on the assistant, on a plan and in a region that offers custom connectors (listed per assistant below).
How sign-in works
- OAuth (use this where offered). Add the server URL and leave any credential fields empty. The assistant opens a "Connect VitalTrends" page, where you paste your API key. The assistant never sees the key, only a token tied to it. The connection is read-only unless you tick "Allow changes to my Training Log" and the key has "Allow workout write access". VitalTrends supports dynamic client registration (DCR) with PKCE, and only issues public clients: there is no client ID or secret to give an assistant that asks for one.
- API key header. Where an assistant can send a fixed
Authorizationheader, useBearer YOUR_API_KEY. The connection gets the key's own permissions. Your account has one API key; regenerating it disconnects every assistant at once.
Data an assistant reads is handled under that assistant's privacy policy. See AI access and your data. VitalTrends does not give medical advice, and neither should an assistant reading your data.
At a glance
| Assistant | Custom remote MCP | Plan or availability | Auth to use | Status |
|---|---|---|---|---|
| Gemini app | Yes, "Custom apps" | US, 18+, personal Google Account, English | OAuth (DCR) | Not yet tested |
| Gemini Enterprise | Yes, admin data store | Google Cloud admin | Needs a client secret | Not supported yet |
| Perplexity | Yes, custom remote connector | Pro, Max, Enterprise | OAuth (DCR) | Not yet tested |
| Mistral Vibe (formerly Le Chat) | Yes, Custom MCP Connector (beta) | Account admin | OAuth (DCR) or Bearer token | Not yet tested |
| Microsoft Copilot Studio | Yes, MCP tool | Copilot Studio in your organization | OAuth (Dynamic discovery) or API key header | Not yet tested |
| Microsoft 365 Copilot | Only through developer-built agents | Tenant admin | n/a | Not supported for end users |
| Microsoft Copilot (consumer) | No documented support | n/a | n/a | Not supported |
| Poke | Yes, integrations | Poke account | OAuth (DCR) | Not yet tested |
| Raycast AI | Yes, MCP servers | Raycast Pro | OAuth (Dynamic) or header | Not yet tested |
| Msty Studio | Yes, HTTP tools | Msty Studio desktop | Header | Not yet tested |
| Jan | Yes, MCP servers | Jan desktop | OAuth or header | Not yet tested |
| Meta AI, DeepSeek app | No | n/a | n/a | Not supported |
Gemini app
Not yet tested Not yet tested by VitalTrends, based on Google's Gemini Apps Help documentation checked 21 November 2026.
Availability: Google lists custom apps for users who are 18 or over and in the US, signed in with a personal Google Account (not work or school), using Gemini in English, with Gemini Apps activity (History) turned on.
- Open gemini.google.com on a computer. Custom apps can only be added on the web.
- Go to Settings → Connected Apps.
- Under Custom apps, select Add a custom app.
- Enter
https://mcp.vitaltrends.net/mcpand select Next. - Leave Advanced features closed: VitalTrends supports dynamic client registration, so no credentials are needed.
- Follow the prompts to the Connect VitalTrends page, paste your API key and select Connect.
Once connected, the app also works in the Gemini mobile app. Type @ in a prompt to pick it. Gemini asks you to confirm write actions. Source: support.google.com/gemini/answer/17209137
If you are outside the US or use a work account, export a CSV (see CSV export) and upload it to Gemini instead.
Gemini Enterprise
Not supported yet Gemini Enterprise lets an administrator add a "Custom MCP Server" data store, but its OAuth setup requires a manually registered client ID and client secret. VitalTrends issues public clients through dynamic client registration only, so there is no secret to enter, and the "No authentication" option is refused by the server. Google's documentation also says the data store supports Streamable HTTP only, not SSE. Source: docs.cloud.google.com/gemini/enterprise/docs/connectors/custom-mcp-server/set-up-custom-mcp-server
Use the REST API or a CSV export instead. A work tenant is also a poor place for personal health data.
Perplexity
Not yet tested Not yet tested by VitalTrends, based on Perplexity's Help Center checked 21 November 2026.
Availability: Perplexity says custom MCP connectors are available to Pro, Max and Enterprise subscribers. On Enterprise, an administrator must allow members to add their own connectors (off by default).
- Open Plugins in the Perplexity sidebar, then select Add custom → Add MCP connector and choose Remote.
- Enter
VitalTrendsas the name andhttps://mcp.vitaltrends.net/mcpas the server URL. - Under Advanced, set Authentication to OAuth and Transport to Streamable HTTP.
- Tick the acknowledgement and select Add.
- Select the VitalTrends connector card to start sign-in. On the Connect VitalTrends page, paste your API key and select Connect.
Perplexity also offers an API Key option, but its documentation doesn't say which header it sends, so use OAuth. Name VitalTrends in your question to make Perplexity use its tools. The Perplexity Mac app doesn't support local (command-based) MCP servers; the remote connector above is the supported path. Source: perplexity.ai/help-center/en/articles/13915507-adding-custom-remote-connectors
Mistral Vibe (formerly Le Chat)
Not yet tested Not yet tested by VitalTrends, based on Mistral's documentation checked 21 November 2026. Mistral renamed Le Chat to Vibe on 12 August 2026; it is still at chat.mistral.ai.
Availability: custom MCP connectors are in beta and only administrators can add them. On Free, Pro and Student plans, the account owner is the administrator.
- Open the Connectors page and select + Add Connector.
- Switch to the Custom MCP Connector tab.
- Enter
VitalTrendsas the connector name (no spaces or special characters) andhttps://mcp.vitaltrends.net/mcpas the server URL. - Select Connect. Vibe detects the authentication method from the server. Complete the Connect VitalTrends page when it opens.
Vibe also supports a Bearer token in the Authorization header, so Bearer YOUR_API_KEY works if you prefer the API key path. To stop Vibe asking before each read, set the read functions to Always allow under My Connectors → Functions; leave write functions on ask. Source: docs.mistral.ai/vibe/work/web/connectors/mcp-connectors
Microsoft Copilot Studio
Not yet tested Not yet tested by VitalTrends, based on Microsoft Learn documentation checked 21 November 2026.
Availability: Copilot Studio is a business product. You need permission to build agents in your organization's environment, and its data policies apply to MCP connectors. Think carefully before connecting personal health data to a work tenant: agents and their connections are governed by your employer's administrators.
- Open your agent's Tools page and select Add a tool → New tool → Model Context Protocol.
- Enter
VitalTrendsas the server name, a short description (for example "Reads my VitalTrends health and training data"), andhttps://mcp.vitaltrends.net/mcpas the server URL. - Choose OAuth 2.0 and Dynamic discovery. Copilot Studio discovers the VitalTrends endpoints and registers itself.
- Select Create, then in Add tool choose Create a new connection, complete the Connect VitalTrends page, and select Add to agent.
Copilot Studio also supports an API key sent as a header. If you use it, set the header name to Authorization and the value to Bearer YOUR_API_KEY; Microsoft's page doesn't say whether it adds the Bearer prefix for you. Copilot Studio no longer supports SSE for MCP, so don't use the /sse endpoint. Source: learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent
Microsoft 365 Copilot: end users can't paste an MCP URL. A developer has to build a declarative agent with an MCP plugin, and the tenant must allow custom apps. Consumer Microsoft Copilot: Microsoft doesn't document custom MCP support. Use a CSV export or the REST API with either.
Poke
Not yet tested Not yet tested by VitalTrends, based on Poke's documentation checked 21 November 2026.
- Go to poke.com/integrations/new.
- Enter
VitalTrendsas the name andhttps://mcp.vitaltrends.net/mcpas the MCP server URL. Leave API Key empty. - Select Create Integration. Poke says servers with dynamic client registration work automatically, so sign in on the Connect VitalTrends page when it opens.
From a terminal, the same thing is npx poke@latest mcp add https://mcp.vitaltrends.net/mcp -n "VitalTrends". Poke's docs don't say how an API key entered there is sent, so use the OAuth path. Source: poke.com/docs/mcp-servers
Poke works over text messages and can set reminders and recurring automations. A good fit is a morning text: "Every day at 7:30, use VitalTrends to text me last night's sleep, today's recovery and yesterday's training in three lines." Check the first few messages against your dashboard.
Raycast AI
Not yet tested Not yet tested by VitalTrends, based on the Raycast Manual checked 21 November 2026. MCP is a Raycast Pro feature.
- Run the Install MCP Server command (or Manage MCP Servers → Install New Server).
- Name it
VitalTrends, choose the HTTP transport and enterhttps://mcp.vitaltrends.net/mcpas the URL. - For OAuth, choose Dynamic and select Sign In. For the API key path, add the HTTP header
Authorizationwith the valueBearer YOUR_API_KEYinstead. - Press Install MCP Server.
HTTP servers also work in Raycast for iOS. Source: manual.raycast.com/ai/model-context-protocol
Msty Studio
Not yet tested Not yet tested by VitalTrends, based on Msty's documentation checked 21 November 2026.
Open Toolbox → Tools → Add New Tool, choose HTTP, enter https://mcp.vitaltrends.net/mcp, and add the header Authorization: Bearer YOUR_API_KEY. Msty Studio does not support SSE. Source: docs.msty.ai/studio/toolbox/tools
Jan
Not yet tested Not yet tested by VitalTrends, based on Jan's documentation checked 21 November 2026.
- Open Settings → MCP Servers and select + Add MCP Server.
- Choose the HTTP transport and enter
https://mcp.vitaltrends.net/mcp. - Turn the server on, then select Sign in on its Auth line to complete the Connect VitalTrends page.
If you set your own Authorization header, Jan uses it as-is and skips OAuth. Tool results are processed by the model you choose in Jan. Source: docs.jan.ai/desktop/integrations/mcp-servers
Assistants without custom MCP
Meta AI, the DeepSeek app and consumer Microsoft Copilot don't document a way to add a custom remote MCP server as of 21 November 2026. You can still use your data with them:
- CSV export: download your data from the Export page in your dashboard and upload the file. See CSV export.
- REST API: if the assistant or its platform can call HTTP APIs, use
https://vitaltrends.net/api/v1with your API key. See the REST API docs.
Troubleshooting
- The assistant asks for a client ID and secret: VitalTrends doesn't issue them. Look for a dynamic registration or "auto" option, or use the API key header if the assistant offers one.
- "Unauthorized" after adding: complete the sign-in step (often a button on the connector card), or check the header is
Authorization: Bearer YOUR_API_KEY. - The connector is added but never used: name VitalTrends in your request, and check the connector is turned on for the conversation.
- Writes are refused: reconnect and tick "Allow changes to my Training Log", and turn on "Allow workout write access" for the key.
- Lab results are missing: lab reports aren't available through MCP or the API. They are in the VitalTrends website only.
For tool names, parameters and general connector problems, see the MCP server reference.