Integration

Slite integration

Team knowledge base API for collaborative documentation. Create and manage notes, organize content in hierarchical collections, search across your workspace, manage users and groups, and use AI-powered features for asking questions. Perfect for building knowledge management integrations, documentation automation, and team collaboration tools.

Connect Slite How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Slite.Built from the 18 Slite tools below, on the connection you add once.

Common Slite use cases

content review workflows
verifying authentication
building user selector UI
resolving user ID to name
resolving group ID to name
building knowledge chatbots
building dashboards in notes
building note tree navigation
editing documentation content
employee offboarding workflows

What you can do with Slite

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Note, 11 operations

archive_noteArchive notePUTArchives or unarchives a note. Archived notes are hidden from normal views but can be restored.
create_noteCreate notePOSTCreates a new note in Slite with title and content. Supports markdown or HTML format, optional parent note placement, and template-based creation.
delete_noteDelete noteDELETEPermanently deletes a note and all its child notes from the workspace. This action cannot be undone.
flag_note_outdatedFlag note outdatedPUTFlags a note as outdated with an explanation reason. Marks content that needs review or update.
get_noteGet noteGETRetrieves a specific note by ID including its full content. Returns note metadata, ownership, timestamps, and content in markdown or HTML format.
get_note_childrenGet note childrenGETRetrieves all child notes of a parent note. Used for navigating the hierarchical note structure and building collection views.
list_notesList notesGETLists notes in the Slite workspace with optional filtering by owner or parent note. Returns note metadata including titles, ownership, and timestamps.
search_notesSearch notesGETSearches notes across the Slite workspace with full-text search capabilities. Filter by parent note, review state, modification date, and archived status.
update_noteUpdate notePUTUpdates an existing note's title, content, or attributes. Provide markdown or HTML for content updates. Supports partial updates.
update_note_ownerUpdate note ownerPUTTransfers note ownership to a different user or group. Provide either userId or groupId to set the new owner.
verify_noteVerify notePUTMarks a note as verified, indicating trusted and up-to-date content. Optionally set an expiration date for the verification status.

User, 3 operations

get_current_userGet current userGETRetrieves information about the authenticated user. Returns email, display name, and organization details.
get_userGet userGETRetrieves a specific user by ID including email, display name, and avatar URL.
search_usersSearch usersGETSearches for users in the Slite workspace by email or display name. Returns matching user profiles with pagination.

Group, 2 operations

get_groupGet groupGETRetrieves a specific group (team) by ID, returning name and member count.
search_groupsSearch groupsGETSearches for groups (teams) in the Slite workspace by name. Returns matching groups with pagination.

Answer, 1 operation

ask_questionAsk questionGETAsk a natural language question and get AI-generated answers based on your Slite knowledge base content. Returns answer with source citations.

Tile, 1 operation

update_note_tileUpdate note tilePUTCreates or updates a tile block within a note. Tiles are structured content blocks that can display title, icon, status, URL link, and rich content.

Use Slite from Claude Code, Cursor or Codex

Connect Slite in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Slite operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Slite

Create your workspace
Sign up free. Nothing to install.
Connect Slite once
Add your Slite connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Slite integration FAQ

What can you do with the Slite integration?

LiveContext exposes 18 operations on Slite, covering note, user, group and answer. Common uses include content review workflows, verifying authentication and building user selector UI.