Skip to main content

Overview

Cleve exposes an MCP (Model Context Protocol) server at:
Once connected, your agent gets read/write access to the same workspace your team uses — notes, folders, skills, memory, and org context. Authentication is handled via OAuth on the first connection. You’ll be prompted to sign in with your Cleve account; no manual token management required.

Quick Start

Run this in your terminal:
After the first connection, you’ll be redirected through the Cleve OAuth flow. Once authorised, the token is stored by your client and reused automatically.
You can also find these snippets in Settings → Developer → MCP Server inside the Cleve app.

Available Tools

Notes

Folders

Skills Marketplace

Memory

Organizations

These tools are available when you belong to one or more Cleve organizations. Org context persists for 30 minutes after switching, then resets to your default.

Authentication Details

The MCP server uses OAuth 2.0 via Clerk. On first connect:
  1. Your client opens the Cleve authorization URL
  2. You sign in with your Cleve account
  3. Your client stores the access token and sends it as a Bearer header on every request
The server reads your user identity and active organization from the token. You do not need an API key for MCP — it’s separate from the REST API key system. If you belong to multiple organizations, use cleve_list_orgs to see them and cleve_switch_org to change context mid-session.

Example Prompts