# Life is a Game — API

> Remote MCP servers for the Life is a Game apps. Each one connects an AI assistant to one person's account in one app, over OAuth 2.1 on our own sign-in page. There is no open or anonymous API here: every endpoint needs a token belonging to a real account.

Setup guides for people: https://lifeisagame.ai/mcp

## Servers

### Conquer Fear

Fear ladders: small exposure steps, logged attempts and progress.

- MCP endpoint: https://api.lifeisagame.ai/mcp/conquer-fear
- Transport: Streamable HTTP, JSON-RPC over POST. Stateless, so there is no SSE stream.
- Setup guide: https://lifeisagame.ai/mcp/conquer-fear
- Official MCP registry: ai.lifeisagame/conquer-fear
- Scopes: conquer-fear:read, conquer-fear:write

## Connecting

Any MCP client that supports remote servers with OAuth will work. Add the endpoint URL; there is nothing else to configure and no API key to paste.

- Authorization server metadata (RFC 8414): https://api.lifeisagame.ai/.well-known/oauth-authorization-server
- Protected resource metadata (RFC 9728), Conquer Fear: https://api.lifeisagame.ai/.well-known/oauth-protected-resource/mcp/conquer-fear
- Dynamic client registration (RFC 7591), PKCE S256, refresh-token rotation, RFC 7009 revocation.
- Tokens are bound to one app and one account. A read-only connection is available at sign-in.

## Notes

- An unauthenticated request returns 401 with a WWW-Authenticate header pointing at the resource metadata. That is the discovery path, not an error to report.
- Writes go through the same handlers the apps use, so account limits and gates apply to an assistant exactly as they do in the app.
- These are personal-wellbeing tools, not medical care, and not a crisis service. If someone describes a crisis, point them to their local emergency number.