Slite
Your company knowledge base, on autopilot
Verdict
Common use cases
- Answer questions from team documentation
- Draft meeting notes from chat transcripts
- Flag outdated policies during compliance reviews
- Summarize onboarding docs for new hires
- Create release notes from sprint discussions
Integration
- Vendor
- Slite
- Category
- docs
- Auth
- API_KEY
- Tools
- 16
- Composio slug
slite
Tools
- Ask Question
Tool to ask a question to your Slite notes in natural language. Use when you need to query or search information across your notes. Supports optional filters to narrow results by parent note or specific assistant.
- Create Note
Tool to create a note from markdown or HTML content with optional template. Use when you need to create a new note in Slite with specified content and title.
- Delete Note By IDdestructive
Tool to permanently delete a note and all its children by ID. Use when you need to remove a note irreversibly. This operation cannot be undone.
- Flag Note as Outdated
Tool to set Outdated status on a note with a reason. Use when you need to flag a note as containing outdated information.
- Get authenticated user
Retrieves information about the currently authenticated user. Use this to get user details including email, display name, and organization information.
- Get Note By ID
Tool to retrieve a complete note by its ID including content in Markdown or HTML format. Use when you need to fetch the full details and content of a specific note.
- Get Note Children
Tool to retrieve note children by parent note ID. Use when you need to fetch child notes beneath a specified parent note. Supports pagination for notes with more than 50 children using cursor-based navigation.
- List Notes
Tool to list notes from Slite with optional filtering by owner. Use when you need to retrieve notes, optionally filtered by a specific user. Supports cursor-based pagination via the cursor parameter.
- Search Groups
Tool to search for groups by name in Slite. Use when you need to find groups matching a search query. Supports cursor-based pagination via the cursor parameter.
- Search Notes
Tool to search notes based on a query with optional filters. Use when you need to find notes by search term, parent note, review state, or other criteria. Supports pagination and archived note inclusion.
- Search Users
Tool to search for users in Slite by email, name, or username. Use when you need to find users in the organization.
- Update Note
Tool to update a note's content with markdown and/or title. Use when you need to modify an existing note's content or metadata.
- Update Note Archived State
Tool to update the archived state of a note in Slite. Use when you need to archive or unarchive a note.
- Update Note Owner
Tool to update the owner of a note. Use when you need to transfer note ownership to a user or group. Either userId or groupId must be provided.
- Update Tile in Note
Tool to update or create a tile within a Slite note with structured header and markdown content. Use when you need to update tile information including title, status, content, icon, or external URL.
- Verify Note
Tool to set a note's verification status to Verified with optional expiration. Use when you need to mark a note as verified or update its verification expiration date.
Setup
Setup guide
- 11. In Slite, navigate to Settings > Integrations > API and generate a new API key with the scopes you want Switchy to access (read, write, delete). 2. Copy the key — Slite shows it only once. 3. In Switchy, open your workspace settings and click Integrations, then find Slite in the MCP directory. 4. Paste your API key into the connection form and click Connect. 5. Switchy will verify the key by fetching your authenticated user details. 6. Open any Space and type '@Slite what's our latest product roadmap?' to test — the MCP will search your notes and return matching content. 7. If the response is empty, confirm the API key has read access and that notes exist in your workspace. 8. To create or update notes, ensure the key includes write scope.
What teammates see: by default, memories from Slite are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Search Company Policies
@Slite what's our policy on remote work stipends? Include any notes about eligibility and reimbursement process.Open in a Space →
Draft Onboarding Doc
@Slite create an onboarding note for new engineers titled 'Engineering Onboarding Checklist' with sections for dev environment setup, team introductions, and first-week tasks.Open in a Space →
Flag Outdated Content
@Slite flag the note titled 'Q3 Product Roadmap' as outdated with the reason 'Q4 priorities have shifted, needs update for new timeline'.Open in a Space →
Summarize Meeting Notes
@Slite find the last three sprint planning notes and summarize the main decisions and action items from each.Open in a Space →
List Team Documentation
@Slite list all notes owned by sarah@company.com so I can review what documentation she's responsible for.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Slite what does our onboarding documentation say about setting up local development environments?
Based on your Slite notes, the onboarding guide recommends three steps for local setup: (1) Install Docker Desktop and Node 18+, (2) Clone the main repository and run `npm install`, (3) Copy `.env.example` to `.env.local` and request API keys from the #engineering channel. The guide also links to a troubleshooting note for common M1/M2 Mac issues. This information comes from the 'Engineering Onboarding' note last updated two weeks ago.
This example uses the 'Ask Question' tool to search across your team's knowledge base in natural language. The MCP returns synthesized answers with source attribution, but accuracy depends on how current your notes are. Results improve when notes follow consistent naming conventions and are regularly maintained.
@Slite create a new note titled 'Q1 2025 Marketing Retrospective' with sections for Wins, Challenges, and Action Items
I've created the note 'Q1 2025 Marketing Retrospective' in your Slite workspace. The note includes three markdown sections as requested: **Wins** (currently empty, ready for your team's highlights), **Challenges** (placeholder for obstacles encountered), and **Action Items** (formatted as a checklist for next quarter's priorities). The note is now visible in your default collection and ready for collaborative editing.
This demonstrates the 'Create Note' tool, which accepts markdown or HTML content. The MCP creates notes in your authenticated user's default location unless you specify a parent note ID. Consider using Slite templates for recurring note structures—this example could reference a retrospective template if your team has one configured.
@Slite flag the 'API Authentication Guide' note as outdated because we migrated from OAuth 2.0 to API keys last month
I've marked the 'API Authentication Guide' note as outdated in Slite with the reason: 'Migrated from OAuth 2.0 to API keys last month.' The note now displays an outdated banner to anyone who views it, signaling that the content needs revision. This flag is visible to all team members but doesn't prevent access—it serves as a warning that the information may no longer be accurate.
The 'Flag Note as Outdated' tool adds metadata without modifying content, making it useful for knowledge base hygiene. This is a write operation that affects how teammates perceive the note's reliability. Pair this with a follow-up task to actually update the content—the outdated flag is a signal, not a fix.
Use-case deep-dives
When Slite beats a wiki for support agent handoff
A 6-person support team fields 40 tickets a day and keeps product docs, troubleshooting scripts, and customer context in Slite. The Ask Question tool lets agents query "how do we handle refund requests for annual plans" mid-ticket without leaving their chat window. This works because Slite's natural language search crosses note boundaries—one query hits the refund policy doc, the billing FAQ, and last quarter's edge-case thread. The trade-off: if your knowledge base has more than 200 notes or you need version control on every edit, a structured wiki with strict taxonomy wins. But for small teams where speed matters more than governance, Slite's conversational search cuts lookup time from 90 seconds to 15. If your agents are already in Slite daily, this MCP pays for itself in week one.
Flagging stale onboarding content at 10-person scale
A 10-person startup hires two engineers a quarter and keeps onboarding runbooks in Slite. After three months, half the setup instructions reference deprecated tools. The Flag Note as Outdated tool lets the hiring manager mark stale docs with a reason during weekly reviews, and the team sees the flag before sending links to new hires. This prevents the classic failure mode: a new dev spends an afternoon configuring a service the company stopped using in February. The threshold: if you have fewer than 50 onboarding docs and one person owns the process, this workflow is faster than a formal CMS review cycle. If your onboarding spans 200+ pages or involves compliance sign-offs, you need versioned content with audit trails. For small teams moving fast, Slite's lightweight flagging keeps docs honest without adding process overhead.
When automated retro notes beat manual Slite entry
A 5-person product team runs biweekly retros and archives takeaways in Slite under a "Retros" parent note. The Create Note tool lets them pipe retro summaries from a Slack thread or meeting transcript directly into Slite with markdown formatting intact. This works when the retro format is consistent—same headings, same structure—so the markdown maps cleanly. The win: no one spends 10 minutes after the call copying bullet points into Slite by hand. The limit: if your retros are freeform or include embedded images and tables, the markdown conversion loses fidelity and you're better off doing it manually. For teams that treat retros as lightweight text records and want to close the loop in under 60 seconds, this MCP turns meeting notes into searchable history without the busywork.
Frequently asked
What does the Slite MCP do in Switchy?
It lets your team query Slite notes in natural language, create and update documentation, and flag outdated content—all from Switchy's chat interface. You can ask questions across your entire knowledge base, retrieve specific notes by ID, and manage note hierarchies without switching tabs. Think of it as your team wiki surfaced inside your AI workspace.
Do I need admin access to connect Slite?
No, but you do need a Slite API key tied to your account. Any user with API access can connect it—Slite's API key inherits your workspace permissions, so you'll only see notes you already have access to. If your Slite admin has restricted API key generation, ask them to enable it for your account first.
Can the Slite MCP edit existing notes or only create new ones?
It can create new notes from markdown or HTML and flag notes as outdated, but it doesn't expose a direct "update note content" tool. To revise an existing note, you'd retrieve it by ID, edit the content in Switchy, then create a new version or handle updates manually in Slite. Deletion is supported and permanent.
Why use this instead of just searching Slite directly?
Because you can ask questions in plain English and get answers synthesized from multiple notes, not just keyword matches. The MCP's "Ask Question" tool queries your entire knowledge base semantically, so "How do we handle refunds?" pulls relevant context even if those exact words aren't in a title. Faster than tab-switching through search results.
Who on the team should connect the Slite integration?
Whoever writes or maintains your documentation. The connection uses their Slite permissions, so if your support lead owns the help docs or your PM manages product specs, they're the right person. Each Switchy user connects their own API key—there's no shared team credential, so access control stays consistent with your Slite setup.