Connect Sutram to Claude in under a minute

MCP server URL

The 3 steps

1. 1

   In claude.ai, open Customize → Connectors.

2. 2

   Click Add custom connector and paste the URL above.

3. 3

   Link, choose the project, and authorize.

Enable file uploads in Claude

Tool calls and file downloads work as soon as the connector is authorized — Sutram streams file bytes through the connector's own host (app.sutram.io), so no extra allowlist entry is needed to read or attach files. File uploads, however, travel directly from your Claude session to AWS S3 via a presigned URL; without allowlisting *.s3.amazonaws.com you will see “network blocked” errors the first time you ask Claude to save a file into Sutram.

1. 1

   In claude.ai, go to Settings → Capabilities and enable Code Execution and File Creation (section names vary by Claude build — look for the outbound network allowlist).

2. 2

   Under Additional allowed domains, add:

   • app.sutram.io — MCP endpoint, OAuth, discovery, and file byte proxy (already required for the connector itself)
   • *.s3.amazonaws.com — direct file uploads via presigned URL (wildcard covers the bucket subdomain returned by S3)

Once Sutram is listed in the Anthropic Connectors Directory, these domains will be declared by the listing and Claude will authorize them automatically — this manual step will no longer be required for new users.

Why uploads bypass Sutram and go straight to S3: the MCP returns a presigned PUT URL scoped to a single object. Bytes travel directly from your Claude session to AWS S3, never through Sutram's servers. The *.s3.amazonaws.com wildcard is broad in name, but the authorization is per-presigned-URL: Claude cannot use this allowlist to reach any bucket beyond the one Sutram signed for.

Claude Free

Claude Free cannot configure a custom domain allowlist and does not have Code Execution. What works and what doesn't:

• ✅ File downloads work directly. When a tool returns a downloadable file, the URL points to Sutram's own host — for example, app.sutram.io/mcp/v2/files/<token>. Sutram streams the bytes from S3 to Claude through this URL, so no allowlist entry is needed and no Code Execution is required. The token expires 15 minutes after issue and authorizes that one file only.
• ✅ Search, navigation, comments, tags, metadata, record creation all work natively, the same as on Pro/Team/Enterprise.
• ❌ File uploads are limited. Uploading a file via MCP requires sending the bytes to S3 from Claude's environment, which needs Code Execution (Pro/Team/Enterprise). Free users should upload through the Sutram web UI — open the target folder, click Add File, then drop or browse the file — and continue the conversation in Claude afterwards.

To use this mode, paste the Sutram Light Preset below into your Claude project's Custom Instructions (Personalization → Custom Instructions, or per-project equivalent). The preset tells Claude to prefer link-based tools and to render every URL as a clickable call-to-action.

You are connected to Sutram via MCP. The user is on Claude without Code Execution and without custom domain allowlist, so you cannot fetch URLs from tool results or transfer file bytes directly.

Operating rules:

1. For file uploads, new versions, or edits, always prefer the `sutram_*_link` tools: `sutram_upload_link`, `sutram_new_version_link`, `sutram_edit_file_link`. These return deep links to the Sutram web app where the user completes the action in their browser. Never call `sutram_request_upload`, `sutram_create_new_version`, or `sutram_checkout_file` in this mode — they return presigned URLs that you cannot execute.

2. When any tool returns a URL, present it to the user as a clear markdown call-to-action: an emoji, a short label, the clickable link, and a note about expiry if applicable. Example: "📥 [Download contract-2026-Q1.pdf](https://app.sutram.io/mcp/v2/files/<token>) (link valid for 15 minutes)". Never display a raw URL as bare text.

3. If the user asks you to read, summarize, or analyze the content of a Sutram file, explain that you cannot fetch the file contents directly in this mode. Offer two options: (a) have them download via the link and paste the content into the chat, or (b) use Sutram's search and metadata tools to answer based on what is exposed without reading the binary.

4. Before any destructive action (`sutram_delete`, `sutram_delete_record`, `sutram_force_release_lock`, etc.), explicitly ask the user to confirm in the conversation, even if the connector has already shown its own permission prompt.

5. Search, navigation, comments, records, and metadata tools (`sutram_search_items`, `sutram_get_folder`, `sutram_get_item`, `sutram_list_comments`, `sutram_create_comment`, etc.) work fully in this mode — use them freely.

Pro track vs Light track