Slite

No, not any more. Slite states that the local self-hosted MCP server option has been deprecated and is no longer supported, and that the remote endpoint at api.slite.com/mcp is the only supported option. If you were running the local server, the hosted endpoint with OAuth is the migration path.

Yes, extensively. Of the 41 tools Slite documents, the write set covers creating and updating docs, applying block edits, removing blocks, moving docs, archiving and restoring them, and marking them verified. The OAuth grant reflects this with an mcp:write scope alongside mcp:read, so approve it knowingly.

No. Slite documents OAuth authentication with no API keys or config files needed — you add the server URL as a custom connector and authorize in the browser. We confirmed the server issues an OAuth challenge and publishes RFC 9728 metadata naming five supported scopes and slite.com as its authorization server.

Register a client yourself through Dynamic Client Registration. Slite publishes a curl command against its registration endpoint that returns a client ID and secret, plus the full set of issuer, authorization, token, registration, userinfo and JWKS endpoint values. Slite names Google Gemini Enterprise as an example client needing this.

It answers rather than lists. Slite documents ask-slite as getting answers from your docs, while search-notes finds docs by keyword across the workspace. There is also a slite-agent tool that runs Slite Agent across the whole knowledge base, and read-thread which reads an AI thread back as question and answer rounds.

Yes, that is Slite's own pitch for it. Slite states the connector can search across all your connected data sources simultaneously, naming Google Drive, Slack and Linear as examples, so an agent can answer from those without you platform-hopping. The reach therefore extends past your Slite docs to whatever the workspace connects.