Connect an external assistant
Greg can give another assistant the context Greg already has: meetings you are allowed to see, email summaries you opted to index, documents, and commitments. Full Greg is required before anyone can connect or call. Preview, expired, and cancelled workspaces cannot.
Connect your assistant
Connections are on for every Full Greg workspace. Each person signs in with their own Greg login and approves the connection themselves. They see only what they can already see in Greg. A teammate's private meeting stays private, and another workspace stays invisible.
ChatGPT
Open Settings → Apps & Connectors, turn on Developer mode under Advanced if your plan asks for it, then choose Create. Name it Greg, paste https://getgreg.io/mcp as the server URL, choose OAuth, and sign in to Greg when ChatGPT opens it. On Business and Enterprise, a workspace admin may need to allow custom connectors first.
Claude (claude.ai and desktop)
Open Settings → Connectors, choose Add custom connector, paste https://getgreg.io/mcp, and choose Connect. On Team and Enterprise, an owner adds the connector for the organisation first.
Claude Code
Install the Greg plugin:
/plugin marketplace add growthable-source/greg-plugins /plugin install greg@greg
Or add the server directly:
claude mcp add --transport http greg https://getgreg.io/mcp
Then run /mcp, choose greg, and sign in to Greg in the browser.
Codex
codex mcp add greg --url https://getgreg.io/mcp --oauth-client-id https://getgreg.io/oauth/clients/codex codex mcp login greg
Codex opens the browser for the Greg sign-in and listens on your own computer for the reply.
An admin can turn connections off for the whole workspace in Settings → Account (Allow external assistants to connect). Allow those apps to report action outcomes stays off until an admin turns it on.
Connection address
Copy the address from Connected apps. On this site it is https://getgreg.io/mcp. Use the address on the settings page. The assistant must support a remote connection over HTTPS, with sign-in and a consent screen.
Greg then asks the person to sign in, if they are not already, and shows the application name, the Greg workspace, and these permissions:
- • See which Greg workspace this connection can use
- • Read your permitted meeting and conversation context
- • Read full transcripts of meetings you can open
- • Read commitments
Uncheck Read full transcripts if you want the assistant to see summaries and action items but not word-for-word transcripts. A connection made before transcripts were offered needs to be reconnected to read them.
Report action outcomes appears only when an admin has enabled that switch. Leave it unchecked unless you want reports written back. Choose Allow. One connection is one person, one workspace, and one app.
Other assistants
Any assistant that supports remote MCP servers over HTTPS with OAuth sign-in can use https://getgreg.io/mcp. It must identify itself with a client metadata document, as ChatGPT, Claude, and Claude Code do.
What the assistant can see
The other assistant does not get Greg's database, your mailbox password, or the ability to send mail, post in Slack, or edit the calendar.
| It can read | It cannot read |
|---|---|
| Meetings you can open in Greg: the list of them, the stored summary, key points, decisions, topics and action items, and the transcript if you granted transcript access | Private meetings you cannot open, and everything in another workspace |
| Email summaries, if you turned on Index my email. These are summaries, not the raw mail | Anyone else's mailbox |
| Documents already in Greg | Calendar as a search index. A meeting brief can still include the start time Greg stored when it joined |
| Commitments on meetings you can see, when you granted commitment access | Slack history. Slack stays inside Greg |
Treat the text it returns as notes. A sentence in a transcript cannot widen what the connection is allowed to do.
How to ask
- Who am I connected as?
- Ask it to check the Greg connection. You should see your name, the workspace, your timezone, and which sources are available. You should not see a list of every member or any token.
- Find the background for a question
- Ask in plain language, for example what you decided about a launch. The assistant searches your permitted meetings, email summaries, and documents. Ask it to cite the meeting or thread.
- What happened in my recent meetings?
- Ask for your meetings from last week, or from a date range. The assistant lists the meetings you can open, newest first, and can then pull one meeting's full summary: the TL;DR, key points, decisions, topics, and action items with their owners.
- What exactly was said?
- With transcript access, ask for the transcript of a meeting, or for the part where a topic came up. The assistant reads it page by page, with speaker labels as Greg stored them. Long meetings take several pages.
- Prepare for one meeting
- Ask it to find the meeting first, then brief that meeting. Greg will not pick a meeting from a fuzzy title inside the brief. Commitments are included only if you granted that permission.
- What is still open?
- Ask what you have committed to. That list defaults to you, and to open commitments. Overdue means the stored deadline has passed.
- Get ready to do one action
- Ask for the context of a specific action the summary or brief already listed. Every action item there carries its id. You get the wording, the owner, the status, and a revision.
Outcome reports
Skip this unless an admin enabled outcome reports and you checked Report action outcomes on the consent screen. The assistant can file a report that it prepared, completed, blocked, or failed an existing action, with a short summary and an optional public https link. Greg stores that report as unverified. The action in Greg stays open. Nothing is emailed, posted, or scored.
If Greg says the action changed, the assistant should fetch the action again and report against the new revision. Repeating the same report is safe. Changing the wording under the same operation id is rejected.
Disconnect
Open Settings → Account → Connected apps and choose Disconnect. The assistant's next call fails. Greg cannot pull back answers that were already returned. Connect again from the assistant when you want access restored. That is a new approval. If the workspace leaves Full Greg, existing connections stop returning data until Full Greg is active again. They are not deleted.