Getting StartedQuickstart

Quickstart

Create your organization, add two sources, build your company memory, connect your AI assistant and get your first answer that joins them.

For the person who creates the organization and becomes its first admin. Plan one sitting: the first build takes a while, and you connect your assistant while it runs. Were you invited instead? Read Get started as a member.

Before you start

  • An AI assistant that supports MCP, such as Claude, Claude Code, Codex, ChatGPT, Cursor or VS Code. MCP is the standard way an assistant uses outside tools.
  • Two places that hold the same topic, so your first question can join them. For example a Notion workspace and your HubSpot deals, or a Notion workspace and a few files to upload.

Create your organization

Go to app.brain.gurusup.com and sign up. Setup is one screen with three steps: Name your organization, Connect your sources and Connect your AI tool.

On Set up your organization, keep the suggested name or type your own, and click Continue. Company size is optional.

You see Where does your team's knowledge live?

Add your sources

Click Connect live sources. You see a card for each app under Live sources, and Drop files and Custom webhook under Additional sources.

  1. Click the plug button on Notion. In the dialog Connect Notion for the organization, check Who can read it (it starts on Default access) and click Connect. Approve access in Notion and come back. Gurusup learns from pages that are created or edited from now on. To bring in older pages, use Import history on the source later.
  2. Do the same for HubSpot. Gurusup learns from deals that change from now on. To bring in earlier deals, use Import history on the source later.
  3. Or click + on Drop files and drop files up to 256 MiB each. The Upload documents panel lists each one under Uploaded files. You can close it with Done while files are still being read.

Each connected source shows a green check labeled Manage. To bring a whole wiki instead, go back with All options and pick Migrate your current wiki. See Import a whole wiki.

Start the build

A line next to the button says how preparation is going, for example "Preparing your content. You can continue while we finish." Click Continue. It reads "Starting…" while Gurusup saves your choice. You don't have to wait for preparation to finish, only for files still uploading, a webhook still being created or an app still connecting.

Gurusup saves your request and starts building by itself once preparation has finished and at least one document is ready. You move on to How will you talk to Gurusup?

Connect your AI assistant

Click the plug button on your assistant's card. A dialog opens.

  • For Cursor and VS Code, the Quick tab has Add to Cursor or Add to VS Code. For Claude Code and Codex, it has a one-line command that installs the Gurusup plugin: click Copy, which shows "Copied.", and paste it in your terminal. For ChatGPT, it has Add plugin from OpenAI, which opens the Gurusup plugin page.
  • For Claude Desktop and Other MCP client, follow the manual steps in the dialog.

Sign in to Gurusup when your assistant asks. Then click Finish. You land on Home, which shows the build progress. Step-by-step pages for each assistant are in the MCP tab.

Wait for the build

Home shows "Getting your documents ready." until the first batch is queued, then "Your memory starts building soon." with Starts in, then "Gurusup is building your company memory." with Time left and a Documents read bar, for example "3 of 12 documents read". The steps Waiting to start, Reading documents and Preparing answers run underneath, and the last stretch reads "Almost ready." Home also tells you that Gurusup emails you when your memory is ready and that you can close the page. Your memory turns on by itself when it finishes, and a banner on every other page shows the time left.

Under While you wait, Connect Claude or ChatGPT, Connect another source and Invite your team are one click away.

Ask a question that joins your sources

Ask your assistant something no single source answers. For example:

"Which open HubSpot deals are past the proposal stage, and what does our Notion pricing page say we can offer them?"

Your assistant asks Gurusup, which searches Brain and returns evidence from both sources. The answer names the Brain pages it comes from. If Gurusup finds nothing, it says so instead of guessing. See Ask questions for how to word questions.

Check that it worked

  • The first sidebar item reads Overview, not Get started.
  • Sources lists each source with a count of memories. See Check source status.
  • Ingest shows your items as Learned. See Follow ingestion.
  • Your assistant answers with pages from more than one source.

What the first build covers

The first build reads a first batch, not everything: up to 25 documents within a size budget, picked in this order: uploaded files and knowledge saved through your assistant, Notion, HubSpot, webhook content, then Slack. The rest comes in through normal ingestion once your memory is active, so with large imports the first answers may not cover everything yet. Reading content uses your usage. See Plan and usage.

If something goes wrong

You seeWhat to do
"Couldn't reach Gurusup" and "Check your connection and try again."Click Try again.
"Sign-in didn't complete. Your browser may be blocking cookies for this site. Allow them and sign in again."Allow cookies for the site, then click Sign in again.
Verify your emailClick Continue to verification.
A reason in red on a file rowRead it, then click Retry (temporary problem) or Choose another file (Gurusup refused the file), or Remove. See Upload content.
"Could not load sources" or "Could not prepare your sources"Reload the page. If it stays, contact support.
"Could not start building your memory"Click Continue again. Your sources are safe.
"Connect a source or upload a file before building your memory."Add a source, then click Continue again.
"Gurusup could not check your content. Your work is safe; contact support for help."Reload. If it stays, contact support.
On a card: "(App) could not read this account. Open the connection above to check its permissions or reconnect."Open the connection and reconnect, or share the content in the app.
On a card: "(App) is temporarily unavailable. Your work is safe; preparation will resume automatically when it responds."Wait. Nothing to do.
On a card: "We could not prepare your (App) content because of a problem on our side..."Wait, or contact support. Preparation resumes on its own.
"Taking a little longer" on the build pageYour files are saved. If it keeps going, click Contact support under "Taking longer than expected?".
"Building your company memory stopped on our side. Your content is safe, new content keeps arriving, and we've been alerted."Click Retry (only admins see it). If there is no button, click Contact support and they finish the build for you. See Overview.

Gurusup drops documents it cannot prepare on its own (failed or rejected files, blocked content, content over your usage), so they never hold up the build.

If you were invited

Your organization already exists and you skip this setup. Follow Get started as a member. An invited admin goes through the setup screens that are still needed: the sources step if the memory is not built yet, the assistant step otherwise.

Next