Your collection, wherever you already are.

How it connects

1. 01

   Open your connectors

   claude.ai → Settings → Connectors

   Under the Customize heading in the settings sidebar. If you land on a pane that says connectors have moved, follow its link — that is the same place.

2. 02

   Add a custom connector

   Add → Add custom connector

   Name it Fraghab and paste the server URL below. Leave the OAuth client ID and secret empty — Claude reads our discovery documents and registers itself.

3. 03

   Authorize Fraghab

   Connect → Allow access

   Claude opens a consent screen hosted by us, listing the four permissions above. You are already signed in here, so it is one click. Choose Not now and you come back unconnected — nothing is half-done.

4. 04

   Set what needs your approval

   Tool permissions

   Claude splits the tools into read-only and write, and asks for approval before every write by default. That default is the right one: leave it on for anything that edits an entry or deducts ml.

What it cannot do

• It cannot delete anything — There is no tool for it — not a bottle, a wearing, a wishlist item, a shelf, a combo, or your account. Archiving is the closest it comes, and archiving is reversible.

• Editing overwrites, and some of it cannot be undone — Changing a field replaces what was there, clearing one empties it, and a logged wearing subtracts ml we keep no prior copy of. Claude asks for approval before running those by default.

• It only ever acts on your own account — The account comes from the credential you approved, never from anything the model says in the conversation.

• Pictures come from our catalog, not from the model — Artwork on anything it adds is matched from Fraghab's own Library. We never fetch an image from an address an assistant supplies.

• A password change revokes it — Changing your Fraghab password revokes every connected assistant immediately, on every device.

How it connects

1. 01

   Turn on developer mode

   Settings → Plugins → Developer mode

   ChatGPT marks it elevated risk, which is the correct label — it is the switch that lets you add a connector nobody has vetted on your behalf. No toggle at all means it has not reached your plan yet; that is an OpenAI rollout and there is nothing to fix here.

2. 02

   Create the connector

   Plugins → +

   Name it Fraghab, paste the description and the server URL below, and set Authentication to OAuth. There is no client ID and no secret to paste — ChatGPT reads our discovery documents and registers itself.

3. 03

   Authorize Fraghab

   Save → Sign in → Allow access

   ChatGPT opens a consent screen hosted by us, listing the four permissions above. You are already signed in here, so it is one click. Choose Deny and you come back unconnected — nothing is half-done.

4. 04

   Use it

   New chat → + / Tools → Fraghab

   Enable Fraghab from the tools menu and write the sentence. While it is unlisted, say “Fraghab” in the prompt — without the name ChatGPT answers from general knowledge instead of from your collection.

What it cannot do

• It cannot delete anything — There is no tool for it — not a bottle, a wearing, a wishlist item, a shelf, a combo, or your account. Archiving is the closest it comes, and archiving is reversible.

• Editing overwrites, and some of it cannot be undone — Changing a field replaces what was there, clearing one empties it, and a logged wearing subtracts ml we keep no prior copy of. Claude asks for approval before running those by default.

• It only ever acts on your own account — The account comes from the credential you approved, never from anything the model says in the conversation.

How it connects

1. 01

   Install it from the Chrome Web Store

   Chrome, Edge, Brave, Vivaldi and Opera all install from the same listing. There is no Safari or Firefox build.

2. 02

   Open the extension and choose Connect

   It shows a short code and waits. The code is good for a few minutes.

3. 03

   Type that code into the pairing page

   Only ever enter a code your own extension is showing you — never one somebody sent you. Approve it and the extension finishes connecting on its own.

What it cannot do

• It never sees your password — Connecting is a one-time approval that hands the extension its own tokens. Your password is never entered into it or stored by it.

• It does not read your browsing history — On a short list of major fragrance retailers its page reader loads with the page; everywhere else it is injected only into the tab you are looking at, at the moment you open it. One page, no record of where you have been.

• Nothing leaves for a third party — Product details go to fraghab.com and nowhere else, only when you click, and only to update your own wishlist. No advertising, profiling or tracking.

• You can cut it off from here — Disconnecting below revokes that browser's tokens immediately. Changing your Fraghab password revokes every connected browser at once.

How it connects

1. 01

   Choose Connect Google Calendar

   Below, in the Your calendar card

   The button hands you to Google's own consent screen. Nothing is stored on our side until you come back from it having agreed.

2. 02

   Approve read-only access

   Google → Continue

   Google names the one permission it is granting, on a screen it has verified us for. Read the line: it should say view events on your calendars, never manage or edit them. Cancel and you land back here unconnected, with nothing half-done.

3. 03

   Come back and check the date

   Your calendar → Connected, with the date

   That line is the proof it took. Your events appear on the dashboard and the wearings calendar from the next load — there is nothing to sync and no wait.

What it cannot do

• It only ever reads — The scope grants no write of any kind, and there is no code path that would use one. We never create, move, edit or delete an event, and never add anything to your calendar.

• Titles and times, and nothing else — An event reaches Fraghab as four things: the date, the title, the start and the end. Attendees, locations, descriptions, attachments and conferencing links are never requested and never stored.

• The suggestion engine never sees a title — Before a day reaches the planner it is reduced to a single coarse word from a fixed list. That word is all the engine receives — not the event, not the title, not a fragment of one.

• One calendar, not all of them — We read your primary Google calendar. The scope cannot list the other calendars in your account, so a shared team calendar or a subscribed feed is invisible to us unless it lands on your primary one.

• The tokens never reach your browser — Google's access and refresh tokens are held server-side, never sent to the page, and never written to a log. Disconnecting deletes them from your row on the spot.