MCP server
Your company's memory, inside your AI
GuruSup Brain connects to Claude and other AI clients through the Model Context Protocol (MCP). Ask a question and Brain answers from everything your team has connected: Slack, HubSpot, Notion and more, with the sources behind each answer.
Connect Brain
Claude
claude.ai, desktop, Cowork and Claude Code
Install the GuruSup Brain plugin. It adds the Brain server and a skill that teaches Claude how to use it.
- In Claude Code, add the GuruSup marketplace and install the plugin:
/plugin marketplace add gurusup/gurusup-brain-plugin /plugin install gurusup-brain@gurusup - The first time Claude uses Brain, a browser window opens. Sign in with your GuruSup Brain account.
Claude Code (server only)
If you only want the tools, without the skill:
claude mcp add --transport http gurusup-brain https://mcp.brain.gurusup.com/mcpThen run /mcp inside Claude Code and sign in.
Other MCP clients
Any client that supports remote MCP servers with OAuth can connect.
- Server URL
- https://mcp.brain.gurusup.com/mcp
- Transport
- Streamable HTTP
- Authentication
- OAuth 2.1 with PKCE. Your client registers itself automatically, so there is no API key to copy.
What you can ask
Brain is most useful when the answer is spread across several tools.
“Prep me for my meeting with Acme tomorrow.”
Pulls the deal from HubSpot, the latest Slack threads and the meeting notes in Notion.
“Why did we change the onboarding flow, and who decided it?”
Finds the discussion in Slack and the decision written up in Notion.
“What have customers said about the new pricing this month?”
Combines HubSpot notes, Slack channels and the documents your team uploaded.
“Nobody documented how refunds are approved. Ask the person who knows.”
Brain finds the right colleague and, once you confirm, asks them for you.
“Save this decision: from October, support hours are 8:00 to 20:00 CET.”
Adds it to company memory so everyone's AI knows it.
Tools
Tools that only read run without asking. Tools that change something or contact someone always ask you first.
init
Loads how Brain works for your account and which skills you can use.
Asks for confirmation: No
health
Checks that Brain is reachable.
Asks for confirmation: No
get_profile
Tells your client which Brain account is signed in.
Asks for confirmation: No
ask_company_memory
Answers a question from your company's memory, with the evidence behind it.
Asks for confirmation: No
search_company_memory
Searches company memory and returns the most relevant results.
Asks for confirmation: No
retrieve_company_memory
Fetches the full evidence for results you picked.
Asks for confirmation: No
start_company_memory_activity
Groups the searches of one task so they are logged together.
Asks for confirmation: No
skills_get
Loads one of your company's skills.
Asks for confirmation: No
add_company_knowledge
Sends new knowledge to company memory. It is processed before it shows up in answers.
Asks for confirmation: Depends on your client
skills_publish
Publishes a skill you wrote. It waits for review before anyone can use it.
Asks for confirmation: Yes
request_human_info
Asks a colleague for information Brain doesn't have, by Slack message or phone call.
Asks for confirmation: Yes, always
request_human_info contacts real people. Claude always asks you before it sends anything, and Brain only contacts colleagues it has selected for that question.
Permissions and data
- You only see what your account can see. Brain answers with the sources your account has access to. Connecting it to an AI client doesn't widen that.
- Every query is logged. Brain keeps an audit record of the questions and searches made through the MCP server, tied to your account.
- No keys in your client. You sign in with OAuth. Your AI client never stores a GuruSup password or API key.
- Your data. Read our privacy policy.