# Connect the assistant you already use

> One address for every assistant. Most connect by pasting it and clicking Connect — no account, no token to copy.

Page: https://revisemy.com/connectors

## The problem

Every assistant adds a connector a little differently, and setup docs drift from what the app actually asks for.

## How ReviseMy fits

Pick your assistant below and follow its two or three steps. The page shows when it’s connected, then you ask for a design checkup.

1. Pick your assistant and follow its steps: paste and Connect, one click, or a try token.
2. This page shows the moment your assistant makes its first call.
3. `create_review` starts a checkup. You mark it, approve or ask for changes, and your agent keeps going.

## Assistants

### Claude (Paste and Connect)

1. In Claude, open Customize → Connectors and choose Add custom connector.
2. Name it ReviseMy and paste the address.
3. Claude opens ReviseMy. Click Connect, and you’re done.

### ChatGPT (Paste and Connect)

1. In ChatGPT, open Settings → Connectors and add a custom connector.
2. Paste the address.
3. ChatGPT opens ReviseMy. Click Connect, and you’re done.

### Cursor (One click)

1. Click Add to Cursor and confirm in Cursor.
2. Cursor opens ReviseMy to sign in. Click Connect.

### VS Code (One click)

1. Click Add to VS Code and confirm in VS Code.
2. VS Code opens ReviseMy to sign in. Click Connect.

### Claude Code (Paste and Connect)

1. Run the command in your project.
2. Run /mcp, choose revisemy, and sign in. Click Connect.

### Grok (Paste and Connect)

1. In Grok, open Connectors → New Connector and choose Custom.
2. Name it ReviseMy and paste the address.
3. Grok opens ReviseMy. Click Connect, and you’re done.
4. If it connects and create_review never shows up, remove it and paste the same origin with /mcp/revisemy-grok. Grok caches a failed URL.

### Muse (With a try token)

1. Get a try token.
2. Paste the message below to Muse. It keeps the token in its own credential store.

### Codex (With a try token)

1. Get a try token, and keep it in a variable with the line below.
2. Add the block to ~/.codex/config.toml.
3. Paste the prompt to Codex once the server is listed.

## A plugin for Claude Code

The ReviseMy plugin adds the server and a design-checkup skill in one step, so Claude Code knows when to ask you for a review.

- In Claude Code, run /plugin marketplace add heyderekj/revisemy, then /plugin install revisemy@revisemy.
- The first checkup signs you in, the same as Connect.

## Reviews right in the chat

In Claude and VS Code, the review opens inside the conversation, so you mark and decide without leaving it. Everywhere else your agent shares the review link. Same loop either way; comments, guest links and the full board live on the link.

- Approving, asking for changes and verifying are yours: those controls exist only for you in the inline view.
- Your agent reads what to do next from get_review, wherever you decided.

## Webhooks for CI

Pass an HTTPS webhook_url to create_review and ReviseMy posts a signed review.decided event when you approve or ask for changes, so a pipeline can wait on you without polling.

- Verify X-ReviseMy-Signature: an HMAC-SHA256 of the raw body, keyed with the review’s owner token.
- Branch on review.status, and read review.next_action for what comes next.
- Later passes inherit the webhook. Addresses inside private networks are refused, redirects aren’t followed, and five failed deliveries in a row pause it.

## Questions

### Do I need a ReviseMy account?

No. Connect makes a try workspace that’s yours, and the people you ask for a review only need its link.

### My assistant isn’t listed.

Any MCP client can use the address. It signs in the same way, or takes a try token as a Bearer header.

### Can my agent approve for me?

No. It creates reviews and reports its fixes. Approving, asking for changes and verifying stay with you.