> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zas.red/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Claude to Zas

> Choose your channels and make Zas available in a Claude conversation.

**1. Prepare your Zas account**

Sign in at [Zas connections](https://zas.red/ai/connect). For organization channels, an administrator must first [enable AI access](https://docs.zas.red/en/ai/enterprise.md).

**2. Add Zas in Claude**

Open [Claude Plugins](https://claude.ai/plugins), then select **Add → Add custom connector**. Some versions call this area **Customize → Connectors**.

| Field | Value |
| - | - |
| Name | Zas |
| MCP server URL | `https://zas.red/mcp` |

Select **Continue**. Keep **Sign in now**. Under **OAuth client**, choose **Use your own OAuth client**.

| Field | Value |
| - | - |
| Client ID | `zas-claude-pilot` |
| Client secret | Leave empty |

Select **Add**, then **Connect**. On Team and Enterprise, an owner first adds or approves the connector in [organization connector settings](https://claude.ai/admin-settings/connectors).

**3. Approve selected channels**

In Zas, confirm your account and choose Read, Send, or both for each channel. Review both confirmations and select **Approve connection**. Original-file sends need Read and Send.

**4. Enable Zas in your chat**

[Start a Claude chat](https://claude.ai/new). In the message box, open **+ → Connectors** and turn on **Zas**. Ask:

> List my approved Zas channels and their permissions.

Then try:

> Save a note titled “First connection” in my “Research” Zas channel: “Connected from Claude.”

Open Zas and verify the note in that channel.

Use the [illustrated guide](https://zas.red/ai/connect) if a setting is hard to find. Your Claude plan and workspace policy determine custom-connector availability.

## Sending a generated file

Claude may need code execution and network access to upload the original bytes. If its sandbox blocks the transfer, check **Settings → Capabilities** and, where your plan or administrator permits, allow `zas.red` as an additional domain. Connector sign-in and sandbox network permission are separate.

When downloading a file, use the address Zas returns. Links for files around 32 MiB and larger use `zas-ai-gateway-7gbbmljqvq-uc.a.run.app` to avoid truncation. If Claude’s code environment blocks that domain, allow that exact hostname where workspace policy permits, or open the item in Zas. Avoid checking temporary links with HEAD: on `zas.red` this can spend one of the three downloads.

A blocked upload has not been sent. Keep the original file and follow the [recovery steps](https://docs.zas.red/en/ai/troubleshooting.md).

Next: [Use your channels](https://docs.zas.red/en/ai/use-zas.md) · [Privacy](https://docs.zas.red/en/ai/privacy.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.