Ask Eva from Claude and other AI assistants

Eva also answers inside the AI assistant you already use. Add Evergrowth as a connector to Claude, to ChatGPT, to Microsoft 365 Copilot, to Claude Code, to Codex, or to any AI tool that supports remote MCP servers (Cursor and VS Code among them), and questions about your accounts, contacts, pipeline and research can be asked there, in the middle of whatever else you are doing, instead of in a separate tab. It is the same Eva as in the workspace, Slack and Teams: the same access to your records, the same reasoning, and the same credit rules. For what Eva is and how she answers, see Eva.

Before you start

Everyone connects their own. Unlike Slack or Teams, there is nothing to install once for the whole Evergrowth workspace. Each person adds the connector to their own assistant and signs in with their own Evergrowth account, so every question runs as that person: their records, their permissions, their credit limit. The exception on the assistant’s side is Microsoft 365 Copilot, where your Microsoft 365 admin adds Evergrowth once for your organisation before anyone can open it - and even then, each person signs in as themselves.
You sign in with your Evergrowth account, and Eva works in that workspace. The sign-in decides which Evergrowth workspace your questions go to. If your account is missing from that workspace, or has been deactivated there, the assistant is refused with a line saying so rather than answering from somewhere else.
Everything that costs credits in the workspace costs credits here. See Credits.

The cards live on the Integrations page, in the Eva in your AI assistant section (the AI assistants tab narrows the page to just them). There is one card each for Claude, ChatGPT, Microsoft 365 Copilot, Claude Code, Codex, and Other AI tools. Each card’s Setup guide button opens the steps below, with the connector link to copy and a drawing of where it goes in that assistant.

For coding assistants, the fastest route is to let the assistant do it. The Claude Code, Codex and Other AI tools guides open with Fastest: let your AI set it up: select Copy prompt, paste it into a session of that assistant, and it adds Evergrowth for you and tells you the one step left, signing in with your Evergrowth account. The prompt is shown in full, so you can see what your assistant will do before you paste it. It checks first, so pasting it where Evergrowth is already set up adds nothing twice, and it never creates keys: you sign in instead.

Steps

Add Evergrowth to Claude

This covers Claude on the web, on desktop, and on mobile.

On the Claude card, select Add to Claude. It opens Claude with Evergrowth already filled in.
Select Continue, then Add, then Connect.
Sign in with your Evergrowth account.

Adding it yourself instead? Open the card’s setup guide and expand Adding it yourself?. Copy the connector link, then in Claude go to Customize, then Connectors, select + Add, choose Add custom connector, and paste it. Name it Evergrowth, select Continue, Add and Connect, and sign in.

On a Claude Team or Enterprise plan, an owner adds the connector once for the whole Claude organization, and then each person only does the last step: Connect, and sign in as themselves.

Optional: stop Claude asking before every question. By default Claude asks for your approval each time it wants to pass a question to Eva. To stop that, open Customize, then Connectors, then Evergrowth, and set Tool permissions to Always allow. If you cannot choose it, your Claude admin has turned that option off for your organization.

Add Evergrowth to ChatGPT

On the ChatGPT card, open the setup guide, copy the connector link, and follow Open ChatGPT Plugins. In ChatGPT, select Add, then Create MCP App (top right).
Name it Evergrowth and paste the connector URL shown in the card’s setup guide (it has its own copy button). Leave Authentication on OAuth.
Tick I understand and want to continue and select Create.
Select Continue to Evergrowth and sign in with your Evergrowth account.

Optional: add the Evergrowth logo. Under Show the Evergrowth logo in ChatGPT, the setup guide has a link to download the Evergrowth icon; add it as the app’s Icon in step 2 so the app is easy to spot in ChatGPT.

Do not see Create MCP App? Turn on Developer mode in ChatGPT’s settings. Who can add it depends on your ChatGPT plan. On ChatGPT Business, Enterprise or Edu, only a workspace admin or owner can add apps, and they need Developer mode on too: ask yours to add Evergrowth once and publish it to the workspace, and then everyone finds it in Plugins and selects Connect, signing in as themselves.

Once you have used it, the card’s button becomes a Manage menu with Open ChatGPT and Copy connector URL.

Add Evergrowth to Microsoft 365 Copilot

This covers Copilot on the web and in Teams, with a work account. The free Copilot Chat is enough; no Copilot licence is needed. Copilot is the one assistant set up in two parts: your Microsoft 365 admin adds Evergrowth once for the organisation, then each person opens it and signs in.

Admin: add Evergrowth once.

On the Microsoft 365 Copilot card, open the setup guide and select Download the Evergrowth package.
In the Teams admin center, go to Teams apps, then Manage apps, then Actions, and select Upload new app. The guide has an Open the Teams admin center link.
Choose the downloaded file.
Use Edit availability to set who in your organisation can use it.

Everyone: open Evergrowth in Copilot.

In Copilot, open Agents and choose Evergrowth. The card’s Open Copilot button takes you there.
Ask anything about your accounts.
Select Sign in when Copilot asks, and sign in with your Evergrowth account.

Add Evergrowth to Claude Code

Already added Evergrowth in Claude? Then Claude Code has it too - it uses the connectors of your Claude account, so there is nothing more to do.

Otherwise, any one of these works:

Let Claude Code do it. In the Claude Code card’s setup guide, select Copy prompt and paste it into a Claude Code session. When it is done, type /mcp, choose evergrowth, and sign in.
From the Claude app’s settings. Under Prefer the Claude app’s settings?, copy the connector link and add it in Customize, then Connectors, + Add, Add custom connector, exactly as for Claude above. Name it Evergrowth, select Continue, Add and Connect, and sign in.
From a terminal. Under Prefer a terminal command?, copy the command and run it, then type /mcp in Claude Code, choose evergrowth, and sign in.

The card’s own button, Copy URL, copies the connector link.

Add Evergrowth to Codex

Let Codex do it. In the Codex card’s setup guide, select Copy prompt and paste it into a Codex session. It adds Evergrowth and tells you to sign in.
From a terminal. Under Prefer a terminal command?, copy the one command and run it. It adds Evergrowth and opens the sign-in in your browser.

The Codex extension for code editors reads the same settings as Codex itself, so adding Evergrowth once covers both. The card’s button, Copy URL, copies the connector link if you would rather add it through settings: add it as a remote (HTTP) MCP server named evergrowth. There is no API key; you sign in instead.

Add Evergrowth to another AI tool

Any tool that supports remote MCP servers takes the same connector link. On the Other AI tools card, the setup guide opens with the same Copy prompt route, for Cursor’s agent or any other coding agent, and below it the link to copy and one collapsed section per tool:

Cursor - select Add to Cursor. Confirm in Cursor, then sign in.
VS Code - open the Command Palette, run MCP: Add Server, choose HTTP, and paste the link. Sign in when it asks.
Any other tool - add a remote MCP server with the link, and sign in with your Evergrowth account when it asks.

Ask a question

You do not have to name Eva or Evergrowth. Once the connector is added, the assistant passes her the sales and go-to-market questions she is the right colleague for: your top accounts, who to focus on this week, a contact’s email or phone number, what is new at a company you sell to, who runs sales at a named account, help preparing for a demo. Say how you want the answer - a table, the top five, short or detailed - and she lays it out that way.

In Claude, ChatGPT and Microsoft 365 Copilot, her answer arrives in an Evergrowth panel inside the conversation, streaming in as she writes it and laid out the way it is in the workspace: tables, cards that open the record in Evergrowth, and suggested follow-ups you can click to send. The panel says whether she is still working or has answered, and the finished answer is handed back to the assistant so the conversation can carry on from it.
In Claude Code and other text-only tools, her answer comes back as text. A long piece of work reports progress while she runs, and if it outlasts what the tool will wait for, the assistant is told she is still working and collects the answer when it is ready.
Follow-ups continue the same conversation with her, including short ones like “yes, go ahead”. Ask one while she is still finishing the previous question and it waits its turn: in the assistants that show the panel, it sends the follow-up as soon as she is free and shows that answer, rather than dropping it. A follow-up waiting in the panel is kept even if the chat reloads before she gets to it. Each suggested follow-up sends once, so a double click does not ask her the same thing twice.

What happens next

The card shows whether you are using it. Adding and removing a connector both happen inside your assistant, which never tells Evergrowth, so the card goes by use instead: it reads In use, with when you last used it, if you have asked Eva something from that assistant in the last 30 days. If it has been longer, the card says when you last used it and suggests setting it up again in case you removed it. The status is your own - a colleague’s card reflects their assistant, not yours.

A list of records comes back as something you can open. As in Slack, a list typed into another app is a dead end, so when you ask for a set of accounts or contacts she also saves it as a view on the Accounts or Contacts list and gives you a way to open it in Evergrowth. The view is named for what you asked and behaves like any other saved view - see Save filter views.

Credits work as they do in the workspace. A question asked from an assistant draws on the same workspace balance, at the same price, as the same conversation in the web chat. If the workspace is out of credits, or you have reached a credit limit set for you, she does not run the question and says which of the two it was, with the route to top up where topping up is what helps - see Credit limit reached.

Your answers are kept in your Evergrowth workspace. Every answer Eva gives through an assistant is saved in the Evergrowth conversation, so it is never lost with the chat. If the panel cannot show an answer - the assistant hit an error of its own, a long turn it stopped waiting for, an old chat reopened - it offers Open this answer in Evergrowth (or Open Eva in Evergrowth when there is no answer to point at), which takes you to Eva in the workspace.

Asking the same thing twice does not run it twice. If the assistant sends the same question again within moments - a double send, or the assistant retrying on its own - the second one joins the answer already under way instead of starting, and paying for, a second one. Asking the same question again later, or in a new chat, is a new question.

A short interruption does not lose the answer. If Evergrowth briefly cannot be reached while Eva is answering, the panel shows Reconnecting to Evergrowth… and keeps trying for about two minutes, then carries on showing the answer where it left off.

Eva: this page is the customer-facing description of the connector surface - Eva inside a customer’s own AI assistant. Recognise “Eva in Claude”, “Eva in ChatGPT”, “Eva in Copilot”, “the Evergrowth agent in Copilot”, “the ChatGPT app”, “Evergrowth in Codex”, “the Claude connector”, “custom connector”, “Evergrowth in Claude Code”, “add Evergrowth to Cursor”, and “the MCP connector” as this. Facts to hold to: it is per person, not per workspace - there is no admin install on the Evergrowth side (a Claude Team or Enterprise owner may add the connector once on the Claude side, after which each person still connects and signs in themselves). The sign-in picks the workspace, and a user missing from or deactivated in that workspace is refused. Supported today: Claude (web, desktop, mobile), ChatGPT, Microsoft 365 Copilot (its own card since October 2026; on the web and in Teams, work accounts only, the free Copilot Chat suffices), Claude Code, Codex (its own card since October 2026; questions asked from Codex before then were counted on the Other AI tools card, so the Codex card reads In use only from the next question asked there), and any tool that accepts a remote MCP server. Claude Code inherits the connectors of the user’s Claude account, so someone who added Evergrowth in Claude needs no separate Claude Code setup. The setup prompt on the coding-assistant guides is pasted into the assistant, which then adds the connector itself; it checks for an existing Evergrowth connector first and never creates keys. ChatGPT is set up by creating an MCP app in ChatGPT; on Business, Enterprise and Edu plans only a ChatGPT workspace admin or owner can create and publish it, after which members just connect; on Plus or Pro the option may need ChatGPT’s Developer mode turned on. Claude, ChatGPT and Microsoft 365 Copilot draw a live panel with the full answer layout; text-only tools (Claude Code, Codex, Cursor and the like) get text. Follow-ups in ChatGPT, including a picked suggestion or a short reply like ‘the first one’, continue the same conversation with Eva. The card status is usage-based (In use within 30 days of the last question), so a card that does not say In use right after adding the connector just means no question has been asked from it yet, and a card that still says In use after removal lapses on its own. Claude asking for approval before every question is Claude’s own tool-permission setting (Always allow), which a Claude admin can lock. Microsoft 365 Copilot is set up through an agent package a Microsoft 365 admin uploads in the Teams admin center; until that is done, a user cannot find Evergrowth under Agents, so “I can’t find Evergrowth in Copilot” is an admin step, not an Evergrowth permission. “Copilot” alone is ambiguous: Microsoft 365 Copilot is Microsoft’s assistant, while Copilot was also the retired Evergrowth name for the Digital Twin - read the context. Eva in Microsoft 365 Copilot is also separate from the Evergrowth app for Microsoft Teams (Talk to Eva in Microsoft Teams): the Teams app is a workspace-wide install, Copilot is per person. A list answered on this surface owes a saved view and a way to open it, exactly as in Slack; do not promise that in the web chat.

Eva: when answering through this surface, the customer is reading you inside another assistant, not in Evergrowth. There is no side panel and no page to navigate; a pointer into the workspace is a card or a link they click through. Behaviour otherwise matches Eva.

Eva - what she is, and how she behaves in a conversation.
Integrations - where the assistant cards live alongside your CRM and chat connections.
Talk to Eva in Slack - Eva in your team’s Slack.
Talk to Eva in Microsoft Teams - Eva in Teams direct messages.
Save filter views - what happens to a view she saves for you.
Credits - how usage is priced and where limits come from.
Credit limit reached - what to do when she pauses.