Review your first diff with hosted MCP.

Connect the remote server, authorize your account, and keep control of the exact change sent for review.

Before you start

This path uses a remote MCP client that supports Streamable HTTP and OAuth.

An Enjoyable account that can complete browser sign-in.
An MCP client that can connect to a remote HTTPS server.
A Git repository with a change you are authorized to submit.

Connect Enjoyable

Add this URL as a remote MCP server in your client. The client should discover the authorization metadata automatically.

url

https://api.enjoyable.work/mcp

OAuth is interactive

Your client opens a browser authorization flow. Sign in, review the requested review:diff scope, and return to the client after approval.

Request the review

Ask the client to construct a unified diff before calling review_diff. Be explicit about staged, unstaged, or branch changes.

Example request

Review my staged changes with Enjoyable.
Create a unified Git diff with three lines of context, submit it to review_diff,
and summarize only the returned findings. Do not send untracked files.

Expected result

The client receives structured findings plus a text fallback. An empty findings array means no qualifying issue was returned; it is not a safety guarantee.