Get startedSetup and authentication

Setup and authentication

Connect your AI assistant to Gurusup with the plugin or steps for your client, or with a pasted prompt, then check that it works.

Any member of the organization can do this, admin or not. For what the assistant gets once connected, see the MCP overview.

Before you start

  • You have an account in a Gurusup organization.
  • You use an assistant that supports MCP. Each one has its own route, shown below.
  • Gurusup answers company questions only once an admin has built the organization's memory. You can connect before that, but the assistant will say Gurusup is not ready. Only an admin starts it: in setup, or by itself once content is ready. See the Quickstart.

Connect your assistant

Open Gurusup MCP in the sidebar and click the plug button on your client's card, or follow the steps below. Members get the same choice on the Welcome screen, under Connect your AI tool.

Run one terminal command that installs the Gurusup plugin. Start or restart Claude Code, run /mcp to confirm gurusup-brain shows up, and sign in to Gurusup. Steps: Claude Code.

On each client, the Manual tab of the dialog shows numbered steps, a snippet to copy and, for most clients, a link to the client's own guide. The snippets use the server name gurusup-brain. Keep it.

Let your assistant do it

An assistant that can edit its own settings, such as Claude Code, Codex or Cursor, can add the server for you. The docs home page has a box called setup-prompt.md, "Paste this into your AI agent". Paste its text into a new conversation and send it. The assistant then:

  • adds the Gurusup server as a remote MCP server over HTTP, named gurusup-brain,
  • restarts itself if its setup needs it, and confirms the server is connected and its tools are listed,
  • saves the instruction from Save the instruction,
  • optionally adds Gurusup's read-only documentation server, gurusup-brain-docs, which needs no sign-in. It uses that server only to learn how to configure and operate Gurusup, never to answer questions about your company.

The first time it connects, your assistant can open a browser window. Sign in to Gurusup there. If you belong to more than one organization, choose it at this step. The assistant then reconnects on its own and lists gurusup-brain as connected. Claude Desktop and ChatGPT cannot edit their own settings, so use their steps above.

More than one organization or account

Sign-in ties a connection to one person in one organization. Everything the assistant does through that connection is for the organization you chose when you signed in. To work in another organization, connect again and choose that one.

To see which account a connection uses, ask the assistant to call get_profile. It returns your email and an opaque profile ID that stays the same for you in that organization. ChatGPT uses this tool to tell connected accounts apart. See ChatGPT.

Save the instruction

Connecting gives the assistant Gurusup's tools. It does not tell the assistant to use them. The prompt on the docs home page saves this instruction for you. If you connected any other way, save it yourself:

For anything about this company, use the Gurusup tools before answering. Call init first, then ask_company_memory. Answer only from what those tools return, and if they find nothing, say so instead of guessing.

ClientWhere the instruction lives
ClaudeProject instructions. It applies only inside that project.
Claude CodeCLAUDE.md in the project
CodexAGENTS.md in the project
Cursor.cursor/rules/gurusup-brain.mdc, with alwaysApply: true
ChatGPTPersonalization, then Custom instructions
VS Code.github/copilot-instructions.md at the root of your workspace. VS Code applies it to every chat request there.
Any other assistantWherever it keeps long-term instructions

The instruction is short on purpose. The detailed rules arrive when the assistant calls init. See How the assistant is told to behave.

Check that it worked

Check the server

Ask the assistant: "Is the gurusup-brain server connected?" It says yes.

Check the tools

The plain address lists the core tools init, health, get_profile, start_company_memory_activity, ask_company_memory, search_company_memory, retrieve_company_memory, add_company_knowledge, report_issue, send_feedback, skills_get, skills_publish and request_human_info, and no more. To also get learn and one tool for each operation your role allows, such as sources_connect, skills_usage or memory_status, connect to https://mcp.brain.gurusup.com/mcp?profile=catalog. A member sees fewer of those than an admin. Some clients show friendlier titles, such as "Ask Company Memory".

Ask a question that needs two sources

Ask something only your joined sources can answer. With HubSpot and Slack connected, for example: "What is the status of our largest open deal, and what has the team said about it in Slack this month?" The assistant asks Gurusup and cites the pages Gurusup returned. If nothing matches, it says it found nothing instead of guessing. See Ask questions.

If it does not work

What you seeWhat to do
gurusup-brain is missing from the assistant's servers or toolsFollow the steps for your client again, or paste the docs prompt
The assistant says Gurusup is not ready to answer company questions yetThe memory has not been built. Ask an admin to check, then try again.
The assistant is connected but does not use GurusupSave the instruction. See Save the instruction.
The assistant works with the wrong organizationConnect again and choose the right organization at sign-in. See More than one organization or account.

For sign-in problems and error messages, see MCP troubleshooting.