Connect Enjoyable to an MCP-capable client.

The hosted server provides one focused review tool without receiving your repository credentials or direct filesystem access.

Server endpoint

Add the HTTPS endpoint as a remote server. Use the URL exactly as shown; the OAuth resource is bound to it.

url

https://api.enjoyable.work/mcp

Authorize your client

1 Start the connection Your client discovers the protected-resource and authorization-server metadata.
2 Sign in and approve Complete browser sign-in and approve the least-privilege review:diff scope.
3 Return to the client The client exchanges the authorization code and can discover review_diff.

Client requirements

The client must support remote Streamable HTTP MCP, OAuth authorization code flow, PKCE with S256, and resource-bound bearer tokens.

Dynamic registration is not advertised

Clients should use supported client metadata or an approved registration. If a client requires a dynamic registration endpoint, contact support before relying on it.