The Descript MCP server ( api.descript.com/v2/mcp ) issues an OAuth access token with roughly an 8-hour lifetime and no refresh_token alongside it. I verified this by inspecting the stored credential in my MCP client: accessToken and expiresAt are present, no refresh token. Because there is nothing to refresh with, every MCP client (Claude Code, Claude Desktop, any other MCP host) is forced through the full browser re-authorization flow every 8 hours. For automation workflows, the main reason to connect over MCP in the first place, the connection dies mid-workday, every day, and a human has to click through the OAuth consent again. Request: return refresh tokens from the MCP OAuth flow (the MCP spec's OAuth 2.1 profile supports the refresh token grant), or offer a longer-lived access token. Either would let MCP clients keep the connection alive without daily manual re-auth. Other MCP servers I use do not behave this way, so Descript's stands out. The MCP integration itself is excellent. This is the one thing keeping it from being reliable for unattended workflows.