Claude, ChatGPT and Codex

Lyba runs an MCP server at https://lyba.io/mcp. Connect your AI assistant to it and the assistant can read your client's feedback — with the page, breakpoint, element and commit each comment was raised on — and act on it: reply, resolve, push a comment to your tracker, start the next round or ask the client for approval.

You sign in through your browser. There are no keys to copy.

Connect

Claude (web and desktop)

In Claude, open Settings → Connectors and add a custom connector.
Enter https://lyba.io/mcp and connect.
Approve the connection on the Lyba page that opens.

Claude Code

bash

claude mcp add --transport http lyba https://lyba.io/mcp

Then run /mcp in Claude Code and choose lyba to sign in. For the Lyba skills too, install the plugin:

bash

/plugin marketplace add playbookTV/lyba-agent
/plugin install lyba@lyba-agent

ChatGPT

Add Lyba from ChatGPT's apps once it's listed. Until then, workspaces with developer mode can add https://lyba.io/mcp as a custom connector, then approve the connection on the Lyba page that opens.

Codex

bash

codex mcp add lyba --url https://lyba.io/mcp
codex mcp login lyba

What happens when you connect

Lyba shows a consent page naming the app (for example claude.ai or chatgpt.com, marked Verified), the agency it will connect to and what it will be able to do. Only continue if you just asked your assistant to connect.

Each connection:

acts as you, with member-level access — it can't manage members, billing, keys or integrations;
appears in Dashboard → Settings → Connected apps, where you can disconnect it at any time;
signs out on its own after 90 days without use.

You'll get an email whenever a new app connects.

What your assistant can do

Tool	What it does	Emails your client
`list_projects`	Lists your projects and their repos	No
`list_sessions`	Finds review rounds by project, repo, branch, PR or commit	No
`get_session`	One round: preview, commit, review link, comparison with the previous round	No
`list_comments`	The client's comments with page, breakpoint, element and commit	No
`get_approval_receipt`	The client's sign-off receipt for an approved round	No
`reply_to_comment`	Replies on a comment thread	Yes — the reviewer is notified
`set_comment_status`	Marks a comment resolved, open or needs discussion	No
`create_review_session`	Creates a round for a preview and returns its review link	Only if you ask it to invite the client
`push_comment_to_tracker`	Opens an issue in your connected Linear, Jira or GitHub	No
`start_next_round`	Starts the next round and carries open comments forward	Yes — recipients get a new invite
`request_client_approval`	Asks the client to sign off	Yes — the client gets the approval link

Assistants ask before running tools that change something, and Lyba's instructions tell them to confirm with you before anything emails your client. Only your client can approve a round — your assistant can ask, never approve.

What your assistant receives

Your projects, review rounds and client comments, including reviewers' names and what they wrote. It doesn't receive your clients' email addresses, review or approval tokens, or recorded reviews.

Comment text is written by your clients. Lyba labels it so assistants treat it as feedback to act on, not as instructions to follow.

The assistant's provider processes what it receives under its own terms. See the privacy policy for how Lyba handles connected apps.

Skills

The Lyba plugin adds two skills to Claude Code and Codex:

lyba-feedback — works through a round's comments on your current branch: finds the code behind each pin, fixes it, then replies and resolves once the fix is committed.
lyba-setup — adds Lyba to a React app: installs @lyba/react, gates it to preview builds and wires @lyba/cli into your CI.

Disconnect

Open Dashboard → Settings → Connected apps and click Disconnect next to the assistant. It stops working immediately.

Questions: review@lyba.io.