Connectors / Knowledge Management
Knowledge Management MCP connectors for Claude, ChatGPT and Cursor
10+ Knowledge Management connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.
https://api.elaichi.ai/mcp
The same for every user.
-
Their own access. An agent never gets more than the person it acts for.
-
One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.
The connectors
Knowledge Management connectors in the catalog
Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.
13 connectors
-
Articulate 360 Hosted sign-in 45 tools
-
Atlan Hosted sign-in 17 tools
-
Butter CMS Hosted sign-in 25 tools
-
Coda Hosted sign-in 18 tools
-
Confluence Hosted sign-in 18 tools
-
GitBook Hosted sign-in 59 tools
-
Google Docs Hosted sign-in 6 tools
-
LearnWorlds Hosted sign-in 5 tools
-
Mem0 Hosted sign-in 37 tools
-
Mintlify Hosted sign-in 16 tools
-
Notion Hosted sign-in 95 tools
-
Quip Bring your own OAuth app 107 tools
-
Strapi Hosted sign-in 31 tools
No Knowledge Management connector by that name
It may sit under another category, or not be in the catalog yet — any documented API can become a connector.
In practice
What teams do with Knowledge Management connectors
Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.
Support
-
Find the runbook without asking around
Search recent Quip threads for the escalation runbook, pull out the relevant steps, and paste the answer into the ticket you are working.
-
Catch up on a thread before a review
Comments are where decisions actually get made and where nobody reads back. Ask for the argument so far in a paragraph, without granting anything that can write.
-
See who can edit the help center
Ask which GitBook members and teams have access to the organization behind your public help center before a big release lands.
Operations
-
Clean up stale invitations and groups
List invitations that were never accepted, remove the ones that are out of date, and tidy groups whose projects have ended.
-
Pull an export for the quarterly review
Start an export of memories in Mem0 and fetch it once it is ready, so the review pack is built from what the assistant actually stored.
-
Onboard a new editor
Create the Strapi user account for someone joining the team, see which roles exist, and confirm what they will be able to do before their first day.
Product
-
Update release notes stored as content
Keep changelog entries, feature descriptions and FAQ items in Butter CMS collections current by changing only the fields that moved.
-
Read the roadmap tracker in plain language
Ask what is marked blocked in the launch tracker table and the agent reads the columns and rows in that Coda doc and answers in a sentence or two.
-
Draft the spec page after the meeting
Turn meeting notes into a new page in the right Confluence space, with the standard headings and labels the team already uses.
People
-
Answer policy questions from the handbook
Ask what the parental leave policy says and get the answer pulled from the actual handbook document in Google Docs, with the wording as it currently stands.
-
Confirm new hires have school accounts
After onboarding week, ask which of the new starters appear in LearnWorlds and which are still missing, and pass the gaps to whoever creates accounts.
-
Build a new hire's reading list
Search Quip for the onboarding guides a new teammate needs and add them as a member on each thread in one pass.
Once it is connected
Things to ask
Each of these is answered against the access the person asking already has, in the Knowledge Management account you connected.
-
Enroll the new support hires in the onboarding course.
-
List all Atlan groups and their member counts.
-
List Butter CMS pages updated in the last week.
-
Summarize the pages in our Q3 planning Coda doc.
-
Summarize pages updated in the Engineering space this week.
-
List GitBook organization members added this month
-
Summarize the documents created in the handbook folder this week.
-
List all LearnWorlds users in the Instructors group.
The tools
What an agent can call in Knowledge Management
- Connectors
- 10+
- Tools
- 479
- Hosted sign-in
- 12
in the Knowledge Management catalog
callable the moment you connect
connect with nothing to register
Of those 479 tools, 7% delete something. Restricting an agent to reads is not a promise here, it is 209 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.
- Read 44%
- 209 tools · list, get, search
- Write 22%
- 107 tools · create, update, send
- Delete 7%
- 34 tools · delete, remove, archive
- Other 27%
- 129 tools · vendor-specific verbs
One endpoint
https://api.elaichi.ai/mcp
Every connector above answers here.
Every Knowledge Management connector, by depth
Tool counts are what the connector exposes today; the split is what those tools do.
Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.
| Connector | Tools | Read · write · delete | Sign-in |
|---|---|---|---|
| Quip | 107 | Your own app | |
| Notion | 95 | Hosted | |
| GitBook | 59 | Hosted | |
| Articulate 360 | 45 | Hosted | |
| Mem0 | 37 | Hosted | |
| Strapi | 31 | Hosted | |
| Butter CMS | 25 | Hosted | |
| Coda | 18 | Hosted | |
| Confluence | 18 | Hosted | |
| Atlan | 17 | Hosted | |
| Mintlify | 16 | Hosted | |
| Google Docs | 6 | Hosted | |
| LearnWorlds | 5 | Hosted |
FAQ
Frequently asked questions
How many Knowledge Management connectors does Elaichi have?
10+ Knowledge Management connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.
Can Claude, ChatGPT and Cursor all use Knowledge Management connectors?
Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Knowledge Management account once makes it reachable from every one of them.
Do Knowledge Management connectors work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Knowledge Management connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.
Do Knowledge Management connectors need me to bring my own OAuth app?
Most do not. 12 of the Knowledge Management connectors use Elaichi's hosted sign-in, with nothing to register. The other 1 ask you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.
Can I stop an agent from writing to Knowledge Management tools?
Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Knowledge Management connector is a matter of allowing the reads and leaving the writes out.
Nearby
Teams that connect Knowledge Management usually connect these too
Put Knowledge Management connectors in front of your team
14 days on Gold, no credit card. Connect one and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.