Every inbox. One place. · Frey in your AI chat
Ask the chat you already use. Let Frey bring the source.
Connect Frey once to an MCP-capable AI chat. Then search across the Gmail and Outlook accounts you chose, prepare meetings, inspect tasks and projects, and surface decisions—without pasting the same context into every new conversation.
Connect Frey once
- 1Finish Frey activation.
Sign in to Frey, connect two distinct Google or Microsoft mail-and-calendar accounts, and confirm they are healthy.
- 2Add Frey as a remote MCP server.
Follow the current ChatGPT or Claude path below and add this exact server URL:
https://askfrey.com/api/mcp - 3Choose OAuth and connect.
Sign in on Frey's authorization screen and review the requested read/write access. Never paste a Frey, Google, or Microsoft password—or a capture key—into the chat.
- 4Enable Frey for the conversation.
In ChatGPT, open a Work chat, type @ and select Frey. In Claude, enable Frey from + → Connectors. Then begin with the account-check prompt below.
ChatGPT
On ChatGPT web, open Settings → Security and login and turn on Developer mode. Open ChatGPT Plugins, select +, enter Frey's server URL and complete OAuth. Install the resulting personal plugin, switch from Chat to Work, type @ and select Frey. If a public Frey listing is later approved, install that listing instead. Availability can vary by account or workspace.
Current official ChatGPT setup guidance ↗Claude
On an individual Free, Pro or Max plan, open Customize → Connectors, select + → Add custom connector, enter Frey's server URL and complete OAuth. Free currently permits one custom connector. On Team and Enterprise, an Owner or Primary Owner first uses Organization settings → Connectors → Add → Custom → Web; members then use Customize → Connectors → Connect. Enable Frey for a conversation from + → Connectors. Mobile installation is currently beta, so web or desktop is the primary setup path.
Current official Claude setup guidance ↗Copy a prompt. Replace the brackets. Start working.
You do not need to remember tool names. Ask in ordinary language, name Frey when the chat has several apps enabled, and state whether you want a read-only answer or a proposed write.
See which accounts Frey can use
Which Google and Microsoft accounts are connected to Frey? Show the provider, account address, and available capabilities for each one.
Expect: A source-aware account list. Use it before asking for work from one exact mailbox.
Open the day with context
What needs my attention in Frey today? Combine my latest brief, meetings, open tasks, and active projects. Separate facts, recommendations, and anything uncertain.
Expect: A grounded overview of the day rather than a generic productivity answer.
Search every connected inbox
Search every connected inbox for ‘[topic, person, or company]’. Group matches by provider and account. Read the most relevant thread and tell me what changed, what I owe, and what needs my judgment. Do not draft or capture anything.
Expect: Relevant threads with the supplying mailbox preserved, followed by a source-grounded read.
Turn the next meeting into a dossier
List my next five meetings. For ‘[meeting name]’, read the Frey dossier and give me the objective, open email threads, likely questions, decisions, owners, and unresolved risks. Keep every source account visible.
Expect: The meeting context Frey already has permission to retrieve. This does not start meeting capture.
Read consented meeting memory
Read the Frey dossier and available consented notes for ‘[meeting name]’. List decisions, owners, due dates, and unresolved questions. Do not create tasks yet.
Expect: Retained meeting context when notes exist. Frey joins visibly with recording off; transcript-only notes begin only after explicit room consent.
Review tasks and projects
Show my open Frey tasks due in the next seven days, grouped by project and owner. Flag tasks without a due date and active projects without a clear next step.
Expect: A bounded review of Frey's existing commitments and projects, without silently changing them.
Use Decision Radar
Using my Frey overview, brief, Postbox, open tasks, and active projects, surface the three open loops most likely to require my decision. For each one, separate evidence, recommendation, uncertainty, and the consequence of waiting. Do not act.
Expect: A decision shortlist for human judgment—not an autonomous decision or external action.
Capture one proposed commitment
Capture ‘Send the revised deck to Mara’ in Frey for tomorrow at 15:00 Europe/Berlin, under the project ‘Launch’, with context ‘Agreed in the investor update’. Keep it proposed for my review.
Expect: One deduplicated proposal. You accept or dismiss it in Frey before it becomes active work.
Save an email draft for review
In my [Google or Microsoft] account [exact email address], draft a reply to the [thread] saying [message]. Keep it unsent and tell me which mailbox Drafts folder received it.
Expect: An unsent draft in one exact mailbox. The chat integration cannot send or delete email.
One real thread. Five turns. No feature tour.
Stay in the same chat and use one real topic. Each turn should carry the same source forward instead of asking you to paste the context again.
- 1Find the source across every inbox.
“Search every connected inbox for [real topic]. Group matches by provider and account. Read the most relevant thread. Tell me what changed, what I owe, and what needs my judgment. Do not draft or capture anything.”
- 2Carry that source into the next meeting.
“Using the source thread you just read, prepare my next meeting with [person or company]. Show the objective, open questions, decisions, owners, and unresolved risks. Keep the supplying mailbox visible.”
- 3After the room, compare memory with evidence.
“Read the available consented notes for that meeting and compare them with the original email thread. List decisions, owners, due dates, and anything that remains unresolved. Do not create tasks yet.”
- 4Organise one agreed next step.
“Propose one task for the agreed next step under [project], with owner, due date, and the source thread or meeting attached. Keep it proposed for my review.”
- 5Check the decision that could still be missed.
“What remaining open loop in this work needs my judgment? Separate evidence, recommendation, uncertainty, owner, and the consequence of waiting. Do not act.”
A simple daily rhythm
| Moment | Ask Frey in the chat | Boundary |
|---|---|---|
| Morning | Overview, brief, meetings, tasks, and three decisions that need you. | Read only; separate fact from recommendation. |
| Before a meeting | Open the dossier and relevant source threads. | Reading prep does not start notes or recording. |
| After a meeting | Read available consented notes; list decisions, owners, and due dates. | Review first; capture only when explicitly asked. |
| End of day | Show open commitments, projects without next steps, and drafts waiting for review. | No send, delete, calendar write, or silent commitment. |
Four habits that make the answers better
- Name the scope. Say “every connected inbox” or give the exact Google/Microsoft account when only one mailbox should be searched.
- Ask for provenance. Request provider, account, thread, meeting, or project sources so evidence stays visible.
- Separate reading from writing. Add “do not draft or capture anything” during research; use “capture” or “draft” only when you want a reviewable result.
- Make the output decisive. Ask for evidence, recommendation, uncertainty, owner, due date, and the consequence of waiting.
- read Today, the latest brief, Postbox, counts, people, and reading context;
- search connected Google and Microsoft inboxes and read a selected thread;
- read meeting dossiers and available consented notes;
- list tasks and projects;
- capture one deduplicated, proposed commitment;
- save an unsent draft in one exact mailbox.
- send or delete email;
- delete Frey data or tasks;
- change calendar events or RSVPs;
- start meeting recording or bypass room consent;
- make a consequential decision for you;
- read an account you did not connect and authorize.