Non-interactive authentication for MCP

We're building a CI pipeline to keep our product demos current. On each release it captures fresh screenshots with Playwright, applies them to a staging copy of each demo, and then promotes the staged steps into the live demo so embeds keep working.

Our workspace API key works on /api/integration/zapier/*, but https://mcp.supademo.com/mcp rejects it with 401 {"message":"Invalid token format"}.

The MCP's OAuth server only supports authorization_code with PKCE. There's no client_credentials grant, and dynamic client registration drops a requested refresh_token grant.

An interactive login gives a 90-day access token with no refresh token, so a person has to sign in again every 90 days to keep CI running.

Could you offer one of these?

- Accept the workspace API key (or a dedicated, scoped API key) as a Bearer token on the MCP server.

- Support the client_credentials grant for a service account.

- Issue refresh tokens, or allow longer-lived tokens for a service user.