← All integrations
Content Sync · AI Actions

Claude (MCP)

Connect your Brainfish knowledge base to Claude. Search, draft, audit, and update your help center content without ever leaving your AI assistant.

Claude (MCP)

Claude MCP Integration: Your Knowledge Base, Working Inside Claude

Your help center holds everything your team knows.

Your product decisions, your terminology, your answers to the questions customers ask every day.

For most teams, that knowledge lives in one place — a tab someone opens when they remember to, and closes when they're done. Claude starts from scratch every session. Your knowledge base and your AI assistant don't talk to each other.

Brainfish MCP changes that.

What Is the Brainfish MCP Integration?

MCP stands for Model Context Protocol — an open standard that lets AI assistants like Claude connect directly to external tools and data sources.

With the Brainfish MCP integration:

  • Claude connects to your Brainfish knowledge base over a secure, authenticated session
  • You can search, read, draft, audit, and update KB content without leaving Claude
  • Every response Claude gives can be grounded in your actual product knowledge
  • Changes push back to Brainfish directly from the conversation

Setup takes under 60 seconds in Claude.ai via OAuth. No config files, no developer required.

How Brainfish Works Inside Claude

When you connect Brainfish MCP, Claude gains five new capabilities:

Find gaps — ask Claude what's missing from your help center before customers find out. Claude searches your entire knowledge base and surfaces topics that aren't covered or are covered too thinly.

Draft articles — paste in a meeting note, a Slack thread, or a product brief and ask Claude to turn it into a publishable help article. The draft goes straight into Brainfish for review, without a copy-paste step.

Audit your KB — ask Claude to inventory your workspace, flag stale articles, surface duplicates, and identify content that hasn't been updated in months. A full KB audit in a single conversation.

Run coverage tests — fire a set of customer questions at your knowledge base and find out which ones Brainfish can't answer confidently. Know your gaps before your customers do.

Update articles — edit outdated content and push changes back to Brainfish from inside Claude. No admin UI, no tab-switching, no context-switching.

Analyse session data — use Claude to pull analytics directly from your Brainfish account: generate session insights, review conversation enrichments, and surface patterns across your knowledge base interactions.

What Changes After You Connect Brainfish MCP

Your Knowledge Base Stops Falling Behind

Before MCP, KB maintenance happened on a schedule — quarterly reviews, sprint-based updates, whoever had time. Updates lagged behind product changes by weeks.

With MCP, maintenance happens whenever you're in Claude. A product update ships, you open Claude, you ask what articles need changing, and you fix them in the same session. The knowledge base stays current because keeping it current no longer requires a separate workflow.

Content Quality Compounds Over Time

Every conversation that surfaces a gap is an opportunity to close it immediately. Every coverage test that reveals a weak spot is an opportunity to draft the missing article on the spot.

Teams that use Brainfish MCP regularly find that their knowledge base improves faster than teams that rely on scheduled maintenance — not because they're spending more time on it, but because the friction between spotting a problem and fixing it is gone.

Your AI Answers Get More Accurate Downstream

Every AI answer Brainfish delivers — in your help center, in Slack, in Microsoft Teams, in your product widget — is only as good as the knowledge behind it.

Keeping your knowledge base current through MCP means every downstream AI answer is more accurate, more specific to your product, and less likely to trigger an escalation.

What Makes This Different from Copying Articles into Claude

Many teams already paste help articles into Claude manually. It works, up to a point.

The problem is that pasting articles means context resets every session. You paste what you remember to paste. You miss the articles you don't know about. And you can't push changes back from the conversation.

Brainfish MCP gives Claude persistent, searchable access to your entire knowledge base — not just what you copy in. It lets Claude act on the KB, not just read from it.

Manual copy-pasteBrainfish MCPResets every sessionPersistent connectionLimited to articles you rememberSearches the entire KBRead-onlyRead and writeNo gap detectionCoverage testing built inUpdates require opening the platformUpdates pushed from Claude

How Teams Are Using It

Buffer uses Brainfish MCP to draft and update Help Center articles from inside Claude, so every product update ships with documentation on the same day — not weeks later when someone finally finds time.

Hearth built a real-time CS conversation guide grounded live in their Brainfish knowledge base, so every support agent responds like the most experienced person on the team, in the moment, without tabbing between docs.

Internal teams use it to run full KB audits and information architecture cleanups without opening the platform once.

Where It Works

Brainfish MCP works inside:

  • Claude.ai — authenticate via OAuth in under 60 seconds from Settings → Integrations
  • Claude Desktop — add to claude_desktop_config.json using your Brainfish API token
  • Cursor — same JSON config as Claude Desktop
  • VS Code Copilot — same JSON config, MCP extension required

FAQ

Do I need to be a developer to set this up?No. The Claude.ai OAuth path takes under 60 seconds with no config files. The JSON config option requires editing a text file, but day-to-day use is entirely conversational.

What can Brainfish MCP read and write?It can search, retrieve, create, and update documents in your Brainfish knowledge base. It can also pull analytics data including session insights and conversation enrichments. An Agent Key is required for answer generation and follow-up tools.

Is my knowledge base data sent to Claude?Only content you explicitly request in your conversation is retrieved and sent to Claude. Brainfish does not proactively push your data anywhere.

Does it work with my existing Brainfish setup?Yes. MCP connects to whichever Brainfish workspace your API token or OAuth session is authenticated against. Your existing collections, articles, and settings are all accessible.

How is this different from the Brainfish API?The API is for developers building integrations. MCP is for teams using Claude as a daily tool — no code required, conversational by default, and designed for knowledge workers rather than engineers.

Keep Exploring

Ship Brainfish + Claude (MCP) this quarter.