MCP Integration

FanDesk supports the Model Context Protocol (MCP), allowing you to connect AI assistants like Claude Code and Claude Desktop directly to your workspace data.

What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI tools securely access your applications. With FanDesk's MCP integration, your AI assistant can:

• Search and manage tasks and projects
• Read and create documents (pages)
• Search emails and send messages
• Check your calendar and schedule meetings
• Browse Google Drive files
• Post messages in chat channels
• Look up contacts
• View and create incidents

Quick Setup

1. Generate an API Key

Go to Settings > Integrations and click Generate Key in the API Keys section. Give your key a descriptive name (e.g., "Claude Code").

Important: Copy the key immediately. You won't be able to see it again after closing the dialog.

2. Connect Claude Code

Run this command in your terminal:

claude mcp add fandesk \
  --transport streamable-http \
  --url https://your-fandesk-domain.com/mcp \
  --header "Authorization: Bearer fdk_your_key_here"

3. Connect Claude Desktop

Add to your Claude Desktop config file (claude_desktop_config.json):

{
  "mcpServers": {
    "fandesk": {
      "url": "https://your-fandesk-domain.com/mcp",
      "headers": {
        "Authorization": "Bearer fdk_your_key_here"
      }
    }
  }
}

How Permissions Work

Each API key inherits the permissions of the user who created it:

• Projects & Tasks - Only projects you are a member or lead of
• Pages - Organization pages, your own pages, and pages shared with you
• Mail & Calendar - Your connected Google accounts only
• Chat - Channels you are a member of
• Incidents - All incidents visible to your organization
• Contacts - Your organization's contact directory

This means the AI assistant can only access data you already have access to. No admin privileges are granted.

Security

• API keys are hashed on our servers (we never store the raw key)
• Keys can be revoked at any time from Settings
• All actions are logged and attributed to your account
• Keys are scoped to your user permissions only