Setting Up the AI Connector

FlawDesk Code provides an MCP server (Model Context Protocol) through which an external AI client can directly access your server — read and write files, modify code, execute builds, start deployments, and run database queries.

Prerequisites

• Access to a FlawDesk project with the Code Connector enabled
• An AI client that supports MCP connections

1. Create a connector token

Every user creates their own token:

1. In FlawDesk: click the ⚙️ icon next to your email address at the bottom of the sidebar → Settings 2. Open the Connectors tab 3. Click + New 4. Enter a name (e.g. the name of the AI tool you want to connect) 5. Copy the displayed token immediately and save it in a password manager — it is only shown once in plain text 6. If lost: rotate the token, the old one is immediately invalidated

2. Add the connector in your AI client

Enter the MCP server URL in your AI client's connector settings. The URL including token is shown directly in the settings — format:

https://mcp.flawdesk.de?token=<your-token>

Client-specific configuration

In FlawDesk, the "Set up" button in the Connectors tab opens a guided assistant that shows the ready-made configuration per client and offers a connection test right after you create the token. The snippets at a glance:

Claude.ai / Claude Desktop

Settings → Connectors → "+" → "Add custom connector". Paste the connector URL and confirm with "Add".

Cursor — ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

{
  "mcpServers": {
    "flawdesk": {
      "url": "https://mcp.flawdesk.de/?token=<your-token>"
    }
  }
}

VS Code — Command palette → "MCP: Open User Configuration" (or .vscode/mcp.json in your project):

{
  "servers": {
    "flawdesk": {
      "type": "http",
      "url": "https://mcp.flawdesk.de/?token=<your-token>"
    }
  }
}

3. Understanding access rights

Which operations an AI client can perform depends on the permission groups the user belongs to in the workspace — the same permissions the user has in FlawDesk, the AI client has through its token. Permissions are configurable under Workspace Settings → Permissions.

Each permission controls its own class of operations:

| Permission | What it allows | |---|---| | View Code Tab & Branches | Read file tree, read files, view git status | | Git write access (push/clone/sync) | git push, clone, edit .gitignore | | Trigger builds | Build modules, start APK/IPA builds | | Trigger deployments | Live deploy to the server | | Execute MySQL queries | Database access through the connector | | Open SSH console | Shell commands through the connector | | Manage connector config & modules | Write/delete files, sticky files, configure modules |

Access is enforced both in the browser and directly via the MCP token — a token cannot perform operations for which the associated permission group is not configured.

Available tools

Files & Code

• flawdesk_code_search — find files, grep in projects (View Code Tab)
• flawdesk_code_file — read files (View Code Tab), write/delete/rename (Manage connector config)
• flawdesk_code_sticky — manage sticky files (Manage connector config)

Git

• flawdesk_code_git — git status/diff (View Code Tab), push/clone/sync (Git write access)
• flawdesk_code_gitignore — edit .gitignore (Git write access)

Build & Deploy

• flawdesk_code_build — build modules (Trigger builds)
• flawdesk_code_deploy — live deployment (Trigger deployments)

Server

• flawdesk_code_mysql — queries against project database (Execute MySQL queries)
• flawdesk_code_exec — shell commands (Open SSH console)

Connector configuration

• flawdesk_code_module — configure modules (Manage connector config)

Tickets

• get_task, list_tasks — read tickets (View tickets)
• create_task — create ticket (Create tickets)
• update_task — edit ticket (Edit own tickets)
• delete_task — delete ticket (Delete tickets)

Common issues

"Connector test failed" — token expired or entered incorrectly. Rotate the token and replace the URL in your AI client.

"Tools available but no access" — check the user's permissions: Workspace Settings → Permissions → edit the user's group.

"No tools listed" — check URL format: must contain ?token= as a query parameter.