Connected assistants

Using Emily from ChatGPT

Emily is in ChatGPT's plugin directory as Emily by White Rabbit Foundry. Install the plugin, connect your Emily account, and ask Emily for things from inside ChatGPT. It's entirely optional - Emily works exactly the same by email and on the dashboard without it.

About 2 minutesWeb, desktop and mobile appsYou approve it on Emily’s own page

Using Claude? Follow the step-by-step Connect Emily to Claude guide.

Before you start

  • An Emily account with a confirmed email address (start a free trial at emily.whiterabbitfoundry.com), and your Emily email and password to hand.
  • A ChatGPT account where plugins are available. In a ChatGPT Business, Enterprise or Edu workspace, an administrator may need to allow the Emily plugin first (ChatGPT Admin > Plugins).

You always approve the connection on Emily's own sign-in screen, in your browser. The assistant never sees your Emily password.

Adding Emily to ChatGPT

  1. Open Emily in ChatGPT’s plugin directory

    Use the Open Emily in ChatGPT link, or in ChatGPT open Plugins and search for Emily. Look for Emily by White Rabbit Foundry.

  2. Install the plugin

    Select Install plugin (on some screens it's a + button).

  3. Connect your Emily account

    Select Connect when ChatGPT asks - now, or the first time you use Emily. Emily's own sign-in page opens: sign in with your Emily email and password.

  4. Review the permissions and approve

    Check the permissions listed, then select Allow connection. You're returned to ChatGPT, connected.

  5. Check it worked

    The connection appears under Account settings, Connected assistants, showing when it was authorised and last used.

Using it in a chat: just ask ("Ask Emily what's on my calendar tomorrow"), type @Emily, or open + and choose Emily under More. ChatGPT shows you what it's about to ask Emily before it runs. It works on chatgpt.com and in the ChatGPT desktop and mobile apps.

Trouble connecting? See troubleshooting below, or email help@emily-wrf.com.

Other compatible assistants

Any assistant that supports custom MCP connectors can use Emily too. Using Claude? Follow the Connect Emily to Claude guide. Otherwise, add a new connector and give it Emily's address:

https://mcp.emily-wrf.com/mcp

Emily's sign-in page opens: sign in, check the permissions and select Allow connection. Some platforms need developer mode or administrator approval for custom connectors.

Using Emily from your assistant

Ask in plain English, the same way you would in Emily's own chat. Each capability and its prerequisites:

FeatureWhat to sayCost
Review your rules and automations"What rules do I have set up in Emily?"Free
Check recent activity"What has Emily done today?"Free
Look up contacts, notes or stored files"What does Emily know about Sam?"Free
Check your usage this period"How many actions have I used?"Free
Ask Emily to do something after confirmation"Ask Emily to reply to Sam and suggest Thursday"Uses actions at the normal rates

Permissions used: up to four, and you approve all of them on Emily's consent screen. openid and email let ChatGPT identify the authorised Emily account using your verified sign-in email. Claude does not ask for these two, so it lists only the other two. emily:read lets the assistant read your rules, automations, recent activity, stored-file details, contacts, memory notes and usage summary. emily:chat lets it ask Emily to answer a question or carry out a task.

Requests can take real actions. Anything you ask through a connected assistant runs through the same Emily engine as the dashboard and email, so it can send email, book meetings and so on, and it uses your action allowance at the normal rates. For anything consequential, the assistant first shows you the prepared plan and only asks Emily to execute it after you confirm. Everything appears in your Activity log exactly as if you had asked Emily directly. An exact retry after a timeout will not run the same prepared action twice.

Supported account changes: after you confirm the prepared plan, Emily can manage rules, automations, contacts, memory notes, preferences and existing saved files through her normal engine. File uploads and file contents are not available to the connected assistant; its direct file view is limited to details such as names and dates, and activity excludes message bodies.

Answers and new requests: when Emily asks you something, just answer - "2" or "the second one" picks from a numbered list. Ask for something new instead and she treats it as a new request rather than an answer, and "no, I meant something else" drops whatever she was doing.

What stays on Emily's website: purchases, billing and subscription changes, paid-address changes and account deletion. A connected assistant cannot prepare or execute those operations.

Removing a connected assistant

You can remove the connection from either side:

  • From Emily: Account settings, Connected assistants, then Disconnect beside the assistant.
  • From ChatGPT: open Plugins, select Emily, then Uninstall plugin. (In a work workspace your administrator may manage this instead.)
  • From another assistant: remove or disable the Emily connector in that platform's own settings.

What happens when you disconnect:

  • Access stops immediately. Emily checks the authorisation on every request, so a disconnected assistant cannot keep working with a credential it already holds.
  • The stored credentials for that authorisation are revoked and expire out of our systems.
  • Your calendars, your other connected assistants and your Emily account are unaffected.
  • Anything Emily already did at that assistant's request stands. Emails already sent and meetings already booked are not undone.
  • You can reconnect at any time; it is the same approval flow again.

Disconnecting in Emily is the more thorough of the two, because it revokes the credential itself rather than only removing the connector on the assistant's side.

To delete your Emily account and all associated data, email Emily "delete my account", or contact help@emily-wrf.com.

How the connection is kept secure

  • Your Emily password is never shared with the assistant. You sign in on Emily's own page and approve the permissions there.
  • The credential issued to the assistant is short-lived and renews quietly in the background. If a renewal credential is ever replayed, the whole authorisation is revoked automatically.
  • We store only a one-way hash of each credential, never the credential itself.
  • An assistant can only ever reach your own Emily account. The account is determined from your sign-in, not from anything the assistant sends.
  • Each authorisation is listed separately in Account settings so you can see what is connected and remove any one of them.

Some platforms share a single authorisation across their desktop and mobile apps, so one entry may cover both. How we handle this data is described in our privacy policy, section 14.

Troubleshooting

SymptomResolution
You can't find or install Emily in ChatGPTUse the direct link and search for "Emily by White Rabbit Foundry". In a Business, Enterprise or Edu workspace, ask your administrator to allow the plugin under Admin > Plugins. Plugin availability can also depend on your plan and region.
Another assistant's connector will not addCheck the address is exactly https://mcp.emily-wrf.com/mcp. Your assistant account may also need custom connector access or administrator approval.
The consent screen will not loadIt opens in your browser and needs you signed in to Emily. Sign in at the dashboard first, then start the connection again.
The assistant says it is not authorisedThe authorisation may have been disconnected or expired. Check Account settings, Connected assistants, and reconnect if it is not listed.
Nothing appears under Connected assistantsThe approval did not complete. Run the connection again and make sure you reach the confirmation at the end.
A request did not do anythingCheck the Activity page on the dashboard. If billing needs attention, or your organisation has switched that action off, Emily says so rather than acting.
You want to be sure what it can seeThe permissions are listed on the consent screen and above. If in doubt, disconnect in Account settings, which takes effect immediately.