Skip to content

Connectors / Knowledge Management

Knowledge Management MCP connectors for Claude, ChatGPT and Cursor

15+ 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.

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

  • Answer a ticket from the knowledge base

    Ask for the current answer to a customer question and get it from Guru, then record a new answer when the team settles something that was missing.

  • 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.

  • 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.

Operations

  • Clean up stale invitations

    List every pending GitBook invite, spot the ones sent months ago to people who never joined, and withdraw them in a single pass.

  • 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.

Product

  • Find entries that have gone stale

    Ask for the entries in a collection that have not changed in months and get a list to work through, with the details of any single one on request.

  • 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.

  • 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.

Marketing

  • Check who can see the campaign calendar

    List the people with access to a spreadsheet and add a colleague as a viewer or editor without hunting through sharing settings.

  • Report on documentation traffic each month

    Gather Mintlify page views, unique visitors and assistant conversations into a monthly summary of which topics drew the most readers.

  • Turn a brief into a first draft

    Point the agent at a campaign brief in Google Docs and have it create a draft blog post or launch announcement in a new document, ready for a human edit.

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.

    Articulate 360

  • List all Atlan groups and their member counts.

    Atlan

  • List Butter CMS pages updated in the last week.

    Butter CMS

  • Summarize the pages in our Q3 planning Coda doc.

    Coda

  • Summarize pages updated in the Engineering space this week.

    Confluence

  • List GitBook organization members added this month

    GitBook

  • Summarize the documents created in the handbook folder this week.

    Google Docs

  • Add a row to the Q3 pipeline sheet for Acme Corp

    Google Sheets

The tools

What an agent can call in Knowledge Management

Connectors
15+

in the Knowledge Management catalog

Tools
794

callable the moment you connect

Hosted sign-in
4

connect with nothing to register

Of those 794 tools, 8% delete something. Restricting an agent to reads is not a promise here, it is 361 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 45%
361 tools · list, get, search
Write 26%
206 tools · create, update, send
Delete 8%
67 tools · delete, remove, archive
Other 20%
160 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. API key and App credentials mean an admin pastes them once, with nothing to register.

Knowledge Management connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
Guru 253 API key
Notion 122 Hosted
Quip 107 Your own app
GitBook 59 API key
Articulate 360 45 API key
Mem0 37 API key
Google Sheets 34 Your own app
Strapi 31 API key
Butter CMS 25 API key
Confluence 19 Hosted
Coda 18 API key
Atlan 17 API key
Mintlify 16 API key
Google Docs 6 Hosted
LearnWorlds 5 API key
Padlet Hosted

FAQ

Frequently asked questions

How many Knowledge Management connectors does Elaichi have?

15+ 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 or any MCP client connects to that same address with OAuth, while the Elaichi Agent reaches the same tools inside the app. 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. 4 of the Knowledge Management connectors use Elaichi's hosted sign-in, with nothing to register. 10 connect with an API key or app credentials that an admin pastes once, with no app to register. 2 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 left out of the model's tool list and cannot be called. Read-only access to a Knowledge Management connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Knowledge Management connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

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
Claude ChatGPT Cursor 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.