MCP Server
What is MCP?
The Model Context Protocol (MCP) is an open standard that lets AI assistants interact with external tools and data sources. clarife exposes an MCP endpoint that gives AI agents access to your workspace.
MCP Endpoint
https://my.clarife.app/api/v1/mcpUses HTTP Streamable transport (POST). Authentication is the same Bearer token used for the REST API.
Setup
Claude Desktop
Edit your claude_desktop_config.json:
{
"mcpServers": {
"clarife": {
"url": "https://my.clarife.app/api/v1/mcp",
"headers": {
"Authorization": "Bearer clrf_your_key_here"
}
}
}
}Restart Claude Desktop to load the new server.
Cursor
Create or edit .cursor/mcp.json in your project root:
{
"mcpServers": {
"clarife": {
"url": "https://my.clarife.app/api/v1/mcp",
"headers": {
"Authorization": "Bearer clrf_your_key_here"
}
}
}
}Cursor detects the file and loads the server automatically.
Claude Code
Run this command in your terminal:
claude mcp add clarife \
--transport http \
https://my.clarife.app/api/v1/mcp \
--header "Authorization: Bearer clrf_your_key_here"Team Workspace
To target a specific workspace, add the X-Workspace-Id header:
{
"mcpServers": {
"clarife": {
"url": "https://my.clarife.app/api/v1/mcp",
"headers": {
"Authorization": "Bearer clrf_your_key_here",
"X-Workspace-Id": "a1b2c3d4-5678-90ab-cdef-1234567890ab"
}
}
}
}Available Tools (36)
The MCP server exposes 36 tools that mirror the REST API. Each tool requires the same scopes as its REST counterpart.
Profile
| Tool | Scope | Description |
|---|---|---|
| get_me | - | Get your profile, plan, usage stats, and API key permissions |
Documents
| Tool | Scope | Description |
|---|---|---|
| list_documents | documents:read | List documents with pagination and filtering |
| get_document | documents:read | Get a document with full content and version number |
| create_document | documents:write | Create a new document |
| update_document | documents:write | Update title, description, or content (optional expected_version) |
| delete_document | documents:write | Soft-delete a document (30-day trash) |
π‘ Tip: update_document accepts an optional expected_version field - the version value from the get_document response. If the document changed in the meantime (editor, another tab, another integration), the update fails with a CONFLICT error instead of silently overwriting - re-read the document, re-apply your changes to the fresh content, and retry. Details: Documents API.
Projects
| Tool | Scope | Description |
|---|---|---|
| list_projects | projects:read | List projects |
| get_project | projects:read | Get project details with document count |
| create_project | projects:write | Create a project |
| update_project | projects:write | Update a project |
| delete_project | projects:write | Delete a project (documents are unlinked, not deleted) |
| move_project | projects:write | Move a project to a folder |
Folders
| Tool | Scope | Description |
|---|---|---|
| list_folders | projects:read | List folders (filter by entity_type) |
| get_folder | projects:read | Get folder details |
| create_folder | projects:write | Create a folder (max 3 nesting levels) |
| update_folder | projects:write | Update a folder |
| delete_folder | projects:write | Delete a folder (cascade deletes child folders) |
Shares
| Tool | Scope | Description |
|---|---|---|
| list_shares | shares:read | List share links |
| get_share | shares:read | Get share with view stats |
| create_share | shares:write | Create a share link |
| update_share | shares:write | Update share settings |
| delete_share | shares:write | Delete a share link |
Media
| Tool | Scope | Description |
|---|---|---|
| create_media_upload | media:write | Get a presigned upload URL |
| confirm_media_upload | media:write | Confirm a completed upload |
Workspace
| Tool | Scope | Description |
|---|---|---|
| get_workspace_info | workspace:read | Get workspace details |
| list_workspace_members | workspace:read | List workspace members |
Brandings
| Tool | Scope | Description |
|---|---|---|
| list_brandings | brandings:read | List branding configurations (Business plan) |
Knowledge Base
Knowledge Base tools require the Business plan - on Pro they return a PLAN_LIMIT_REACHED error.
| Tool | Scope | Description |
|---|---|---|
| list_knowledge_bases | kb:read | List your bases |
| get_knowledge_base | kb:read | Get a base with categories and entries |
| update_knowledge_base | kb:write | Update base settings |
| create_kb_category | kb:write | Create a category (tree up to 3 levels) |
| update_kb_category | kb:write | Update a category |
| delete_kb_category | kb:write | Delete a category |
| create_kb_entry | kb:write | Add an entry from a share link |
| update_kb_entry | kb:write | Update an entry |
| delete_kb_entry | kb:write | Delete an entry |
Resources
The MCP server provides documentation resources that AI clients can read to understand document formats and workflows:
| Resource URI | Description |
|---|---|
| clarife://guides/content-format | Complete guide to block types, required fields, and the image upload workflow |
| clarife://guides/knowledge-base | Knowledge Base publishing workflow (document β share β entry), categories, and limits |
π‘ Tip: AI clients can read clarife://guides/content-format to learn the exact block schema before creating or updating documents. This resource documents all block types (heading, text, screenshot, image, divider, code, table) with required fields and examples.
Example Prompts
Once connected, you can ask your AI assistant things like:
- "List all my clarife documents"
- "Create a new document called 'API Integration Guide' with step-by-step instructions"
- "Upload this screenshot and add it to the setup guide"
- "Share the onboarding tutorial with a password"
- "Show me the members of my workspace"
- "Publish this tutorial to my Knowledge Base, in the Getting started category"
π‘ Tip: Grant your MCP API key only the scopes the AI assistant needs. For read-only exploration, documents:read and projects:read are enough.