Integrations
Email, Slack, a signed webhook, and connecting Claude with MCP.
Send review activity to the tools you already use. Owners and admins set these up in Settings → Integrations. Credentials stay on your server.
There are four events: a new client comment, a client sending feedback, the next round being ready, and an approval. Each integration has its own on/off switch per event.
Email is sent through Plunk. It's turned on on the server with the PLUNK_API_KEY setting.
- You get an email when a client sends feedback or approves.
- Your client gets an email when a round is ready (if the project has a client email), and a copy of their approval.
- An email for every single new comment is off by default. Turn it on if you want it.
Press Send test email to check it works. The test goes to your own address.
Slack
- In Slack, create an incoming webhook for the channel you want.
- Paste its URL into Incoming webhook URL.
- Choose the events, then Save Slack settings.
Each message has the person's name, the project, the text and a link.
Webhook
For your own automations (Zapier, Make, n8n or your own code).
- Enter an Endpoint URL. It must be HTTPS.
- Enter a Signing secret.
- Choose the events, then Save webhook settings.
Review Studio posts JSON for each event: event, projectId, projectName, author, text, url and timestamp.
Checking the signature. Every request has an X-Review-Signature header: sha256= followed by the HMAC-SHA256 of the raw request body, using your signing secret. Compute the same on your side and compare before trusting the request.
MCP (connect Claude)
MCP lets an AI assistant such as Claude read your reviews, reply to comments, resolve them and add internal notes.
- Copy the Endpoint from the MCP card (it ends in
/api/mcp). - In Claude (claude.ai custom connectors, Claude Desktop or Claude Code), add it as a remote MCP server.
- When asked, sign in with your studio email and password, check what the app can do, and press Allow.
Replies the assistant writes use your name. Each connection shows under Connected apps, where you can Revoke it. Disabling an account cuts off its access straight away.
Fallback: MCP_TOKEN. If the server has an MCP_TOKEN set, a client can also connect with the header Authorization: Bearer <token>. Sign-in is the better option: each person gets their own connection and you can revoke one without affecting the others.
Browser extension
See Browser extension.
Was this helpful?
Your feedback shapes what we write next.