MCP server · Thrive Global

thrive

Thrive Global operates an official remote MCP server at https://mcp.thriveglobal.com/mcp (Streamable HTTP with SSE fallback), documented on the Thrive Global Partner API Portal. Each user authenticates individually via OAuth 2.0 / OpenID Connect against Thrive's Keycloak identity provider; MCP clients discover the OAuth endpoints automatically and must identify with the client ID thrive-mcp-server. Read tools require the user:mcp role; the single write tool (checkin_to_microsteps) requires user:mcp-rw. Tool list captured verbatim from the portal's MCP page.

Open endpoint → Thrive Global provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Thrive Global Type: Hosted endpoint Transport: http Host: mcp.thriveglobal.com

Endpoint

https://mcp.thriveglobal.com/mcp

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "thrive-global": { "url": "https://mcp.thriveglobal.com/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "thrive-global": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.thriveglobal.com/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://mcp.thriveglobal.com/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

get_user_wellbeing_status — Fetch the user's current wellbeing status: their Thrive Score (0-100) with a per-behaviour breakdown, plus sleep and activity signals derived from wearables over the last 7 days.
get_intention — Fetch the user's current daily intention. Returns a fallback message object when no intention has been set.
get_daily_tasks — Fetch the user's daily task list: the currently active time of day plus each scheduled item with its position, completion state, and associated entity (microstep, check_in, article, thrive_reset, personalized_reset).
get_recommended_wellbeing_content — Get wellbeing content recommended for the user - a normalised mix of articles and daily journey steps.
get_reset_for_user — Get a Thrive Reset (a short guided video) for the user. Each item includes pre-rendered markdown_content suitable for rich rendering.
get_microstep_content — Get microstep recommendations for the user, sorted by popularity. Each microstep carries the journeys it belongs to.
get_article_content — Get article recommendations for the user (text and video articles), including like counts and the user's reading/watching progress.
checkin_to_microsteps — Check the user in to one or more microsteps. Requires write access (the user:mcp-rw role). Parameters: microstep_ids (string[], required), date (ISO date, optional, defaults to today).
search_wellbeing_content — Full-text search across Thrive wellbeing content (articles, microsteps, resets), ranked by relevance. Parameters: query (string, required), limit (number, default 20).

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.