How to Connect Slite to Claude (and What It Can't Do)
Good news first: Slite is one of the easier knowledge bases to hook up to Claude, because Slite ships an official, hosted MCP server — announced in the Slite changelog — at https://api.slite.com/mcp. No community code to vet, no server to run, no API key to rotate. It follows the authenticated remote MCP spec: paste the URL into Claude as a custom connector, OAuth into your workspace, done. Two constraints still apply, and they’re Claude’s rather than Slite’s: custom connectors require a paid Claude plan, and the connection only does anything inside a conversation you’ve started.
Setup in about two minutes
- In Claude, open Settings → Connectors and choose Add custom connector.
- Enter
https://api.slite.com/mcp. - A Slite login window appears; authorize it. Because auth is OAuth against your own account, Claude sees exactly the docs and channels you can see — workspace permissions carry through, which matters if your Slite has restricted channels for leadership or HR.
That’s the whole procedure. Compared to the tools in this series that need self-hosted community servers, Slite is the low-friction outlier.
What Claude can do inside your knowledge base
Slite’s MCP exposes the operations that map to how teams actually use it — searching docs, asking questions across the workspace (the same ground Slite’s own Ask feature covers), creating and updating notes, and even reading comment threads with their participants and resolved state. Realistic asks:
- “Search our Slite for the travel expense policy and quote the per-diem section exactly.”
- “Draft a decision doc in the Product channel summarizing this thread, using our usual decision-record format.”
- “What changed in the engineering onboarding docs over the last month, and are any comments still unresolved?”
For a docs-heavy team this is a real upgrade over copy-pasting into a chat window: Claude cites from the actual current doc rather than a stale paste, and it can write its output back into Slite as a note instead of leaving it stranded in the conversation.
The gap between “answers questions” and “runs your docs”
Everything above is pull, never push. Claude will retrieve the QA checklist when asked; it will never notice that the checklist changed. In knowledge-base terms, the misses look like this:
- Your product sync ends at 3pm. The meeting note that should exist in the Product channel by 3:15 doesn’t — unless someone opens Claude, prompts it, and pastes the transcript in.
- A teammate publishes a new security policy. The Slack announcement, the email to affected teams, the “please re-read” nudge: all manual. Publishing a doc can’t start a Claude chat.
- Docs go stale silently. Nothing reviews the workspace weekly and flags the pages nobody has touched since the last reorg.
Slite’s own AI (Ask) has the same boundary — it answers questions in the moment. Neither it nor Claude’s connector acts on events.
Where Carly picks up
Carly is an AI executive assistant designed around exactly those events. Its workflows start from triggers — a meeting ending, a doc being published, a weekly schedule — and run in the cloud, so the follow-through happens whether or not you’re at a keyboard.
Tell it “after every product sync, write the meeting note into our Slite Product channel and post the link in #product”, in those words. Carly interviews you about specifics (which meetings count? what format?) and then constructs the workflow with you — no flowchart builder, no MCP endpoint to babysit. It records meetings, sends real email through Gmail and Outlook, posts to Slack, and keeps tasks updated alongside the docs. AI agents start at $35/month, and any workflow steps that don’t use AI run free and unlimited. See the Slite integration page and the rest of the 200+ integrations.
The two roles, compared
| Claude + Slite MCP | Carly | |
|---|---|---|
| Search docs and answer from them | Yes (official hosted MCP) | Yes |
| Create or update a note on request | Yes | Yes |
| Writes the meeting note itself when the meeting ends | No | Yes |
| Announces newly published docs to the team | No | Yes (Slack, email) |
| Scheduled doc-freshness reviews | No | Yes |
| Setup | Paste one URL + OAuth (paid Claude plan) | Guided conversation |
| Pricing | Paid Claude plan | AI agents from $35/mo |
Frequently Asked Questions
Does Claude integrate with Slite?
Yes — and unusually cleanly. Slite hosts an official MCP server at api.slite.com/mcp that you add to Claude as a custom connector with OAuth. You’ll need a paid Claude plan, since custom connectors aren’t available on the free tier.
Is the Slite MCP server official?
Yes. It’s built and hosted by Slite (see their changelog announcement), follows the remote MCP spec, and respects your workspace permissions — Claude can only reach docs your account can reach.
Can Claude create a Slite note automatically after a meeting?
Not on its own. The connector works only inside chats you start, so post-meeting notes still require a human to prompt them. If you want the note written and shared the moment the meeting ends, that’s a trigger-based agent job — Carly does it end to end.
Will Claude see private channels in my Slite workspace?
Only if you can. Auth is per-user OAuth, so Claude inherits your permissions — restricted channels stay restricted.
How does Slite’s own Ask compare to Claude over MCP?
Ask lives inside Slite and answers from your workspace; Claude over MCP answers from the same content but can combine it with everything else in the conversation and write new notes back. Both stop at Q&A — neither reacts when docs change or meetings end.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Claude knowledge base · Claude + Outline · Claude + Recall.ai · Claude + tl;dv
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
