Leadership checking in on deals. Sales engineers call prepping before their discovery calls. AEs keeping tabs on their open opps.
All situations where having some form of centralized knowledge base saves everyone on the GTM team hours of their day.
In this post we’ll show you how we set up one such knowledge base using a few common MCPs, and some custom tooling.
Architecture
We’re going to lean heavily on Vercel’s brand new agent builder framework eve. This is an excellent starting point that lets us start with a pre-optimized harness that we can build on.
We’ve tried to build agents from scratch, and getting the agent to regularly use the tools available at its disposal is a much harder task than we thought.
Eve eliminates this class of problems and lets focus on the task at hand.
With eve, we’ll set up 3 core tools:
Slack’s MCP
Notion’s MCP
Slack and Notion should be relatively straightforward, we use their publically available MCP endpoints to pull in conversation history, product notes, etc.
Turbopuffer may need some explanation.
This is an extremely fast storage solution that we’ll be feeding in Hubspot CRM data into. The reason for this is Hubspot, while they do have an MCP, is extremely slow and limited with their search functionality. Ingesting Hubspot data daily into Turbopuffer means we can do full text search across our CRM, we can do regex filtering, and vector-based semantic searching all extremely quickly without the Hubspot API limitations.
These are the two core methods of expanding our knowledge base — new MCPs, or new data in Turbopuffer.
MCP Connections
Our Slack and Notion MCP connections require some form of OAuth authentication.
Though this is in beta, Vercel’s new Connect tool does a great job of spinning up these managed OAuth connectors. Depending on your use case, you can either have one user log in and share their credentials and access for slack/notion, or configure Eve to request the user connect their own account to the tools.
The latter may be preferable if your team is larger and managing sensitive conversations in slack, or private pages on Notion is important.
Either way, Vercel Connect will spin up the OAuth connection as required by Slack or Notion, generate those OAuth consent screens, and give tokens to our agent to make the MCP calls.
Channels
Eve supports many channels on which the agent can live. By default the agent can be exposed as a CLI, accessible via a eve dev https://url.to/your/agent
Other channels can be easily built into:
Slack
Discord
Microsoft Teams
Telegram
Twilio
GitHub
Linear
Eve also supports building custom UIs, in case you wanted to run the knowledge base in a totally standalone app UI — can do this using the Chat SDK or just using the API provided by eve.
Code
Our knowledge base code is fully open source, available here.