Path: Connectors → Knowledge Base
What this connector does
The Knowledge Base connector is a free, pre-connected MCP integration that exposes your Wazzi-hosted KB articles to AI tools. Unlike Asana or High Level, there's nothing to set up — every Wazzi org has it on by default.
You'll still want to know it's there because:
- It exposes its own MCP URL for your team to paste into Claude / ChatGPT to let the AI search and read your KB.
- It has its own permissions in Managing Permissions under MCP Connectors → Knowledge Base.
- It powers other Wazzi features (the public KB portals you set up in Knowledge Base — Portals).
What this connector lets your team do
Once a user has KB MCP permissions, they (or their AI assistant) can:
- Search KB articles by keyword: "find articles about onboarding".
- Read full article content: "pull up the article on returning a damaged unit".
- List articles in a portal: "what guides exist for vendors?"
- (With create perms) draft new KB articles based on conversations.
This is the most-used connector at most orgs, because it lets every internal AI assistant act as a help desk for your own documentation.
Why is it pre-connected?
Two reasons:
- Your KB lives in Wazzi. There's no external system to authenticate against — the data is already here.
- Knowledge Base is included on every Wazzi plan. It would be weird to charge an "integration" fee for connecting Wazzi to itself.
What you'll see on the edit page
Open the KB connector edit page from the catalog. The Configuration tab shows the Connected status and a brief note that no setup is required:
The Access tab works just like any other connector — copy the MCP URL, paste it into your AI tool. See Connecting Claude or Connecting ChatGPT.
Best practices
- Keep KB content fresh. AI tools that search a stale KB hand customers stale answers. Set a quarterly review cadence.
- Mark sensitive articles "Authenticated only". The KB connector respects portal access levels — public portals are visible to public AI assistants on your domain; authenticated-only portals require sign-in. See Knowledge Base — Portals.
- Grant only Read on the KB connector for most groups. Create permissions should be limited to a KB Authors group with a clear review workflow.
Frequently asked questions
Can I disable the KB connector?
Yes — the Disable button is on the Knowledge Base product page (/knowledge-base). Disabling the product turns off both the public portal and the MCP connector.
Does the KB connector expose draft / unpublished articles?
No. Only published articles in enabled portals are exposed via MCP.
How are KB permissions enforced for the AI?
The MCP server checks the calling user's group permissions on every call. An AI agent acting on behalf of a user with no KB read perms gets a permission-denied error.
What's next
- Set up portals to control who sees what: Knowledge Base — Portals.
- Brand your KB with a custom theme + domain: Knowledge Base — Domains and Knowledge Base — Theme.
- Restrict which actions the KB connector exposes: Managing Permissions.