---
title: "Connect SideDrawer to Claude: Control Folders and Collaborators"
slug: connect-sidedrawer-to-claude-control-folders-and-collaborators
date: 2026-09-07
author: Riya Sethi
categories: ["AI & Agents"]
excerpt: "Learn how to connect SideDrawer to claude using Truto. Step-by-step guide to tool calling, API quirks, and autonomous workflows."
canonical: https://truto.one/blog/connect-sidedrawer-to-claude-control-folders-and-collaborators/
---

# Connect SideDrawer to Claude: Control Folders and Collaborators


If your team needs to connect SideDrawer to Claude to automate secure document collection, manage client vaults, or audit collaborator permissions, you need a [Model Context Protocol (MCP) server](https://truto.one/what-is-model-context-protocol-mcp/). This server acts as the translation layer between Claude's tool calls and [SideDrawer's REST API](https://truto.one/sidedrawer-api-integration-guide/). You can either build and maintain this infrastructure yourself, or use a managed integration platform like Truto to dynamically generate a secure, authenticated MCP server URL. If your team uses ChatGPT, check out our guide on [/connect-sidedrawer-to-chatgpt-manage-drawers-and-file-workflows/](https://truto.one/connect-sidedrawer-to-chatgpt-manage-drawers-and-file-workflows/) or explore our broader architectural overview on [/connect-sidedrawer-to-ai-agents-sync-records-and-audit-actions/](https://truto.one/connect-sidedrawer-to-ai-agents-sync-records-and-audit-actions/).

Giving a Large Language Model (LLM) read and write access to a highly secure digital vault like SideDrawer is an engineering challenge. You have to handle API token lifecycles, map nested ontology schemas to MCP tool definitions, and deal with SideDrawer's strict document lifecycle states. Every time SideDrawer updates an endpoint or deprecates a legacy resource, you have to update your server code, redeploy, and test the integration.

This guide breaks down exactly how to use Truto to generate a secure, managed MCP server for SideDrawer, connect it natively to [Claude Desktop](https://truto.one/connect-claude-desktop-to-any-api-via-mcp/), and execute complex document management workflows using natural language.

> Want to give your AI agents secure, authenticated access to SideDrawer and 100+ other SaaS APIs? Let's talk about [managed MCP architecture](https://truto.one/managed-mcp-server-for-llms/).
>
> [Talk to us](https://truto.one/book-a-demo/)

## The Engineering Reality of the SideDrawer API

A custom MCP server is a self-hosted integration layer. While the open MCP standard provides a predictable way for models to discover tools, the reality of implementing it against specialized secure document APIs is painful. SideDrawer is built to manage highly sensitive financial, legal, and personal records. Its API reflects that security-first complexity.

If you decide to build a custom SideDrawer MCP server, here are the specific integration challenges you will face:

**The Drawer-Hanger-Record Ontology**
SideDrawer does not use a flat file system. It enforces a strict taxonomy: Drawers (the top-level vault) contain Hangers (record types like "Tax Documents"), which contain Folders (records), which finally contain Files. Creating a simple folder requires passing exact `recordTypeName` and `recordSubtypeName` values alongside the `sidedrawer_id`. An LLM cannot simply guess these hierarchical constraints. A managed MCP server exposes tools that strictly define these schemas, explicitly guiding Claude to provide the correct payload structure without hallucinating invalid record types.

**Granular Collaboration and Network IDs**
Access control in SideDrawer is highly dimensional. You do not just "share a file." Collaborators are defined by a `contributorType` (Account, Team, or Invitation), assigned a specific `sidedrawerRole` or `recordRole`, and bound by an `expiryDate`. Modifying access requires querying across networks and translating standard user emails into SideDrawer-specific network IDs. 

**Cryptographic File States**
Files in SideDrawer transition through states like `quarantined` and `sealed`. Sealing a file makes it immutable, generating specific compliance logs. Interacting with these files requires handling correlation IDs and file tokens rather than simple file paths. If your MCP server does not correctly map these state transitions to distinct JSON-RPC tools, the LLM will fail to execute critical security workflows.

## Generating the Managed SideDrawer MCP Server

Truto solves these problems by dynamically generating MCP tools from SideDrawer's API documentation and your configured integration resources. Tools are never pre-built or cached - they are derived at runtime. A tool only appears in your MCP server if it has a corresponding documentation record, ensuring that only curated, well-described endpoints are exposed to Claude.

You can generate your SideDrawer MCP server in two ways: via the Truto UI or programmatically via the API.

### Method 1: Creating the Server via the Truto UI

For teams who want a zero-code deployment, the UI is the fastest path:

1. Navigate to the integrated account page for your connected SideDrawer instance in the Truto dashboard.
2. Click the **MCP Servers** tab.
3. Click **Create MCP Server**.
4. Select your desired configuration. You can restrict the server to specific methods (e.g., read-only) or specific tags (e.g., only tools tagged with "collaborators").
5. Copy the generated MCP server URL (e.g., `https://api.truto.one/mcp/a1b2c3d4e5f6...`).

### Method 2: Creating the Server via the API

For platform engineers embedding AI into their own applications, you can provision SideDrawer MCP servers dynamically. Truto verifies that the integration is AI-ready, generates a cryptographically secure token, stores it in an edge-distributed key-value store, and returns the endpoint.

```bash
curl -X POST https://api.truto.one/integrated-account/{integrated_account_id}/mcp \
  -H "Authorization: Bearer YOUR_TRUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "SideDrawer Onboarding Agent",
    "config": {
      "methods": ["read", "write"],
      "tags": ["folders", "files", "collaborators"]
    },
    "expires_at": "2026-12-31T23:59:59Z"
  }'
```

The `methods` and `tags` arrays act as a quality gate. The Truto API validates that the intersection of these filters produces at least one valid, documented tool. If it does not, the request is rejected, preventing you from deploying an empty server.

## Connecting SideDrawer to Claude

Once you have your Truto MCP server URL, connecting it to Claude requires no additional middleware. You can configure this via the Claude interface or manually via a configuration file.

### Method 1: Via the Claude UI

1. Open Claude Desktop or the web interface.
2. Navigate to **Settings > Integrations > Add MCP Server**.
3. Paste the Truto MCP server URL into the URL field.
4. Click **Add**.

Claude will immediately perform a JSON-RPC handshake (`initialize` and `tools/list`), reading the SideDrawer schemas directly from Truto.

### Method 2: Via Manual Configuration File

For teams managing Claude Desktop deployments centrally, you can define the server in Claude's `claude_desktop_config.json` file. Because Truto provides the endpoint via Server-Sent Events (SSE), you use the official remote transport module.

```json
{
  "mcpServers": {
    "sidedrawer_prod": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-sse",
        "https://api.truto.one/mcp/YOUR_SECURE_TOKEN_HERE"
      ]
    }
  }
}
```

## Handling SideDrawer Rate Limits

When orchestrating high-volume operations - like auditing hundreds of collaborators - [rate limiting](https://truto.one/how-to-handle-api-rate-limits-in-ai-integrations/) becomes a factor. 

Truto's proxy architecture enforces a strict pass-through policy for rate limits. Truto does not silently retry, throttle, or apply exponential backoff on your behalf. If the SideDrawer API returns an HTTP 429 Too Many Requests, Truto passes that error directly back to Claude. Truto normalizes the upstream rate limit information into standardized IETF headers (`ratelimit-limit`, `ratelimit-remaining`, `ratelimit-reset`). 

It is entirely the responsibility of the caller (your application framework or LangChain implementation) to parse these headers and manage retry logic.

```mermaid
sequenceDiagram
    participant Claude as Claude Desktop
    participant Truto as Truto MCP Server
    participant SideDrawer as SideDrawer API

    Claude->>Truto: Call side_drawer_files_list_all
    Truto->>SideDrawer: GET /v1/records/{id}/files
    SideDrawer-->>Truto: 429 Too Many Requests
    Truto-->>Claude: Error: 429 with IETF headers
    Note over Claude: Client parses ratelimit-reset<br>and waits before retrying
```

## Hero Tools for SideDrawer

The Truto MCP server exposes SideDrawer's capabilities as distinct, schema-validated tools. Here are the core tools you will use to build automated document workflows.

### side_drawer_drawers_get_home_lite

Retrieves a lightweight dashboard summary of a specific Drawer, including owner details, current status, and a breakdown of folder types. This is the best tool for giving Claude initial context about a client's vault before drilling into specific records.

> "Claude, pull the dashboard summary for the Smith Family Trust drawer and tell me how many Tax and Legal folders currently exist in the vault."

### create_a_side_drawer_folder

Creates a new Folder (record) within a SideDrawer. This tool requires the LLM to provide the specific ontology mapping, including the `recordTypeName` (Hanger) and `recordSubtypeName`.

> "Create a new folder in the Smith Family Trust drawer for their 2026 Corporate Tax Returns. Map it under the Tax hanger and use the standard corporate tax subtype."

### list_all_side_drawer_files

Lists all files within a specific SideDrawer folder, returning metadata including upload status, file size, and whether the file has been quarantined or sealed.

> "Audit the 2025 Onboarding folder and list all files. Flag any files that are larger than 50MB or are currently marked as quarantined by the security scanner."

### side_drawer_collaborators_list_by_drawer_or_folder

Audits who has access to a specific Drawer or Folder. This returns the network identities, role assignments, and expiration dates of all contributors, which is critical for compliance reporting.

> "Pull the full list of collaborators for the Acme Corp drawer. Identify any external accountants whose access is set to expire in the next 30 days."

### create_a_side_drawer_drawer_collaborator

Provisions access to a SideDrawer. The LLM uses this tool to invite users, assign them specific roles (like Viewer or Editor), and optionally enforce an expiration date for temporary audit access.

> "Add audit@example.com as a collaborator to the Q3 Financials drawer. Assign them read-only access and set their permission to automatically expire next Friday."

### side_drawer_files_seal_by_name

Locks a file, making it immutable. Sealing a file is a one-way security operation in SideDrawer that prevents future modifications, making it essential for finalized contracts or filed tax returns.

> "Find the 'Final_Signed_Contract_2026.pdf' file in the Legal folder and execute the seal operation to make it immutable."

To see the complete inventory of available SideDrawer tools, including endpoints for batch operations, template applications, and file quarantine workflows, visit the [SideDrawer integration page](https://truto.one/integrations/detail/sidedrawer).

## Workflows in Action

Connecting Claude to SideDrawer allows you to chain these tools into complex, multi-step operations. Here are real-world examples of how AI agents interact with the vault.

### 1. Client Vault Provisioning

Wealth management and accounting firms often need to spin up standardized structures when onboarding new clients.

> "Claude, create a new tax folder for the client in their main drawer. Once created, invite their external CPA (cpa@example.com) as a collaborator with an expiration date set for the end of tax season (April 30th)."

**Execution steps:**
1. Claude calls `create_a_side_drawer_folder` with the `sidedrawer_id` and maps the new folder to the "Tax" record type.
2. Claude extracts the newly created `record_id` from the response.
3. Claude calls `create_a_side_drawer_drawer_collaborator`, passing the CPA's email, the required role, and the ISO-8601 formatted expiration date.

**Result:** The client vault is successfully provisioned and the third-party auditor is granted time-bound, compliant access.

### 2. Security Audit and File Sealing

Compliance teams use Claude to monitor vault integrity and enforce document immutability after review cycles.

> "Audit the Q4 Compliance folder. If you find the finalized audit report document, seal it. Then, pull the list of collaborators on that folder and verify if anyone still has write access."

```mermaid
flowchart TD
    A["Start<br>Audit Workflow"] --> B["list_all_side_drawer_files<br>Query Q4 Folder"]
    B --> C{"Is Final Report<br>Present?"}
    C -- "Yes" --> D["side_drawer_files_seal_by_name<br>Seal Document"]
    C -- "No" --> E["Alert User"]
    D --> F["side_drawer_collaborators_list_by_folder<br>Fetch Access List"]
    F --> G["Analyze Roles<br>Report Write Access"]
```

**Execution steps:**
1. Claude calls `list_all_side_drawer_files` to retrieve the contents of the target folder.
2. Identifying the final report, Claude extracts its exact file name and extension.
3. Claude calls `side_drawer_files_seal_by_name` to permanently lock the file.
4. Claude calls `side_drawer_collaborators_list_by_folder` and analyzes the JSON response to flag any users with editor/admin roles.

**Result:** The user receives confirmation that the document is cryptographically sealed, along with a warning list of users who still retain write access to the parent folder.

## Security and Access Control

Exposing a secure document vault to an LLM requires strict boundary setting. Truto's MCP architecture provides four distinct layers of access control for your SideDrawer servers:

*   **Method Filtering:** Limit your MCP server to non-destructive operations. By setting `methods: ["read"]` during server creation, you ensure Claude can list files and view collaborators, but absolutely cannot delete folders or modify permissions.
*   **Tag Filtering:** Restrict tool generation to specific API domains. If you only want Claude auditing access, you can filter by `tags: ["collaborators"]`, entirely removing the LLM's ability to see or interact with files.
*   **Secondary Authentication (`require_api_token_auth`):** By default, possessing the MCP URL grants access. By enabling this flag, you force the client (Claude Desktop or your custom agent) to also provide a valid Truto API token in the `Authorization` header, preventing unauthorized execution if the URL is leaked.
*   **Auto-Expiring Servers (`expires_at`):** You can bind the MCP token to an expiration date. Once the timestamp is reached, Truto's Durable Object alarms automatically purge the token from the edge KV store and database, revoking LLM access instantly.

## Moving Forward

Integrating SideDrawer with Claude transforms a static document vault into an active, conversational workspace. By utilizing a managed MCP server, you offload the complexity of hierarchical schema mapping, token lifecycle management, and rate limit header normalization.

Instead of burning engineering cycles maintaining point-to-point connector code, your team can focus on orchestrating high-value compliance, provisioning, and auditing workflows.

> Ready to connect SideDrawer and dozens of other enterprise APIs to your AI agents? Get started with Truto's managed MCP infrastructure today.
>
> [Talk to us](https://truto.one/book-a-demo/)