Why KnowStack? The Complete Workflow How Features Connect Use Case Examples Getting the Most Value
Creating Your Account First Login & Dashboard The General Flow: From Data to Knowledge Understanding Navigation
Website Crawling Email Integration Document Upload Meeting Transcripts Telegram Integration Slack Integration
Generating a Knowledge Base Iterative Generation
Viewing & Navigating AI Search Editing Content Version Management Exporting Access Control
Inviting Team Members Roles & Permissions
Profile Settings Company Settings Notifications
Plans & Pricing AI Usage & Billing
Data Protection Account Security Secure Integrations
Integration Overview Claude Connector Managing Integrations
Overview Creating a Test AI Question Generation Assigning Tests The Candidate Experience AI Grading and Manager Override Analytics Releasing Results Abandonment and Retakes FAQs Troubleshooting
Tracking Activity
Getting Help Common Issues
Common Questions

Claude Connector

Every other integration brings knowledge into KnowStack. The Claude connector sends it the other way: it lets Claude read your knowledge bases directly while you work. Ask Claude a question in its own app and it looks the answer up in KnowStack instead of guessing.

Claude reads the live knowledge base, so an edit you make in KnowStack appears in Claude's next answer. There is nothing to re-upload and nothing to keep in sync.

The Claude connector requires a Business plan.

Setting It Up

  1. An owner of your Claude Team or Enterprise workspace opens Settings, then Connectors, then Add custom connector.
  2. They give it a name and paste your connector address, shown in KnowStack under Settings, then Integrations.
  3. They leave OAuth Client ID and Secret empty. Claude fills those in itself.
  4. Everyone else enables the connector and signs in to KnowStack once, from Claude.

What Each Person Sees

Signing in ties the connection to that person's KnowStack account. Claude then reads only the knowledge bases they can already open in KnowStack, and nothing else.

  • During sign-in each person chooses which of their knowledge bases to share. Leaving them all ticked also covers knowledge bases created later.
  • Access is read-only. Claude cannot edit, delete, or reach anything outside the knowledge bases that were shared.
  • If someone loses access to a knowledge base in KnowStack, it disappears from their Claude connection too, without reconnecting.

What Claude Does With It

ToolWhat it does
list_knowledge_basesShows which knowledge bases are available
list_kb_sectionsLists the sections of one knowledge base
search_kbFinds the sections that match a question
get_kb_articleReads a section, and everything nested under it, in full

Claude chooses these itself; you never call them by name. Ask a question in ordinary language, in whichever language your knowledge base is written in.

Ending a Connection

Settings, then Integrations, lists everyone who has connected Claude, when they connected, and when they last used it. Disconnecting someone there stops Claude reading through that connection. People can also disconnect from Claude's own Connectors screen.

Tokens for Scripts and Command-Line Tools

Outside the Claude apps, for example the Claude Code CLI, you can generate a connector token instead. It is under Settings, then Integrations, in the advanced section.

A connector token is not tied to a person, so it reads every knowledge base in the company regardless of individual permissions. Use it for scripts you control, not as a way to give a colleague access.