Slite MCP Server

Official remote MCP server for the Slite knowledge base. Search docs, create and edit notes, manage comments, channels, and collections via OAuth.

Collaboration by Slite OAuth2 active

Connect (Remote Server) Docs

Overview

The Slite MCP server is the official, provider-hosted Model Context Protocol endpoint for Slite, a team knowledge base and documentation platform. It lets AI assistants like Claude and ChatGPT search, read, write, and reorganize content in a Slite workspace while respecting the workspace's existing permissions. The server follows the authenticated remote MCP spec and is hosted at https://api.slite.com/mcp, so there are no local processes to run or API keys to manage. Authentication is handled via OAuth at connection time.

Capabilities cover the full document lifecycle: searching and retrieving notes, creating and updating documents with formatting and icons, modifying individual content blocks, moving documents between channels, and archiving or restoring them. The server also exposes collection management, channel creation and configuration, comment threads (global or anchored inline), and discovery tools for users and groups. Recent updates have added pagination on hierarchy traversal, expanded search filters, change tracking with bot indicators, and access to Slite's Knowledge Management Panel data.

Because it is centrally hosted by Slite, setup is a single URL plus an OAuth flow in the MCP client. This makes it notably easier to deploy than community alternatives that require a self-hosted Node process and a manually managed API key.

Tools

Tool	Description
`search-notes`	Search notes across the workspace with filters and pagination.
`get-note`	Retrieve a specific note by ID in markdown or HTML.
`get-note-children`	List child notes under a parent for hierarchy traversal.
`ask-slite`	Ask a natural language question answered against workspace content.
`create-note`	Create a new note with markdown content, optional icon shape and color.
`update-note`	Update a note's title, content, or icon.
`modify-block`	Edit a specific block within a note, including native Slite blocks like callouts, tables, and mermaid diagrams.
`move-note`	Move a note to a different parent or channel.
`archive-note`	Archive a note.
`restore-note`	Restore a previously archived note.
`create-comment`	Create a comment thread on a note, global or anchored inline to a span of text.
`read-comments`	List all comment threads on a note with history, participants, and resolved state.
`resolve-comment`	Mark a comment thread as resolved or unresolved.
`create-collection`	Create a new collection.
`update-collection`	Update collection name or metadata.
`create-channel`	Create a public, private, or read-only channel with an optional icon.
`update-channel`	Rename a channel, change its icon, or update visibility.

Setup Guide

Prerequisites

A Slite workspace and account with permission to authorize integrations
An MCP client that supports remote, OAuth-authenticated MCP servers (Claude Desktop, ChatGPT, Cursor, etc.)

Connection

The server is centrally hosted by Slite. There is nothing to install. Point your MCP client at:

https://api.slite.com/mcp

Authentication uses OAuth at connection time, so no API keys or config files need to be managed manually.

Claude Desktop config (remote MCP)

Add an entry under mcpServers in claude_desktop_config.json:

{
  "mcpServers": {
    "slite": {
      "url": "https://api.slite.com/mcp"
    }
  }
}

On first use, Claude Desktop will open the OAuth flow to authorize the connection against your Slite workspace.

Other clients

For ChatGPT, Cursor, and other MCP-compatible clients, add a new remote MCP connector pointing at https://api.slite.com/mcp and complete the OAuth flow when prompted.

Use Cases

Answer support and onboarding questions by searching the Slite knowledge base in natural language with ask-slite and search-notes.
Draft and publish weekly status notes or postmortems from chat: create-note with markdown, then move-note into the right channel.
Keep docs current by having an agent run search-notes on a topic, then call modify-block to patch outdated sections.
Triage feedback loops by listing open threads with read-comments, replying via create-comment, and closing them with resolve-comment.
Bootstrap a new team space: create-channel for the team, create-collection for project docs, and seed initial notes from a template.

Example Prompts

"Search Slite for our incident response runbook and summarize the on-call rotation steps."
"Create a new note in the Engineering channel titled 'Q3 Planning' with these sections as markdown..."
"Find every Slite doc that mentions the deprecated billing API and add a callout block warning that it's been removed."
"List all unresolved comment threads on the Onboarding guide and reply to each with the answer from this thread."
"Create a private channel called 'Launch War Room' with a rocket icon and move the launch checklist note into it."

Pros

Official, vendor-hosted server: no local install, no API key handling, OAuth-based auth
Broad coverage of the Slite data model, including native blocks (callouts, tables, mermaid), comments, channels, and collections
Actively maintained with frequent updates (pagination, expanded filters, knowledge management panel access)
Respects existing workspace permissions for the authenticating user

Limitations

Remote-only and tied to Slite's cloud, no self-hosted option
Requires an MCP client that supports OAuth-authenticated remote MCP servers
Public tool schemas are documented mainly via Slite's changelog rather than a dedicated reference page

Alternatives

fajarmf/slite-mcp: community, self-hosted Slite MCP server using a Slite API key (more limited than the official server).
Zapier MCP for Slite: routes Slite actions through Zapier's MCP endpoint if you already use Zapier.
Notion or Confluence MCP servers: comparable knowledge base integrations if your team uses those platforms instead.