> ## 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 Grok to Zas

> Read approved Zas channels and save results from Grok web through the hosted connector.

Connect Grok web once, then use Zas in your conversations while your Zas browser is closed. You choose the channels and permissions Grok receives.

> [!NOTE]
>
> Using the Grok dashboard? [Open Add MCP server](https://grok.com/dashboard/plugins?mcp=add). Set **Name** to `Zas`, **Transport** to `HTTP`, **URL** to `https://zas.red/mcp`, and **OAuth client ID** to `zas-grok-web`. Leave **HTTP headers** and **OAuth client secret** empty. Select **Add server**, then follow the sign-in prompt and choose your channels in Zas. The steps below show the separate Grok web form.

**1. Add a custom connector**

In [Grok Connect Apps](https://grok.com/connectors), select **Add a custom connector**.

| Field | Value |
| - | - |
| Name | Zas |
| Server URL | `https://zas.red/mcp` |
| Headers | Leave empty |

Select **Add MCP**. A managed workspace may require administrator approval first.

![Grok server form with Zas, https://zas.red/mcp and empty Headers.](https://zas.red/media/ai-guide/grok-v1/server.webp)

**2. Configure OAuth**

When **OAuth Credentials Required** appears, use:

| Field | Value |
| - | - |
| Client ID | `zas-grok-web` |
| Client Secret | Leave empty |
| Authorization Endpoint | `https://zas.red/oauth/authorize` |
| Token Endpoint | `https://zas.red/oauth/token` |
| Scopes | `zas.read`, `zas.send`, `offline_access` |
| Token Auth Method | **none (PKCE only)** |

Grok discovers the endpoints and scopes automatically. Select **Save & Connect**.

![Grok OAuth settings: zas-grok-web, empty Client Secret and none (PKCE only).](https://zas.red/media/ai-guide/grok-v1/oauth.webp)

**3. Choose channels in Zas**

Sign in to your registered Zas account and check the account shown. Choose **Read**, **Send**, or both for each channel. Original-file sends need both permissions. Organization channels also need [admin approval](https://docs.zas.red/en/ai/enterprise.md).

Review the confirmations and approve the connection. This approval lets Grok renew access until the connection expires or you disconnect it.

![Example Zas account approving Read and Send for Product ideas in Grok.](https://zas.red/media/ai-guide/grok-v1/permissions.webp)

**4. Try Zas in a conversation**

Open [a new Grok chat](https://grok.com/) and ask:

> Use Zas to list my approved channels and their permissions. Read the latest note in my test channel.

To test sending, choose a channel with Send permission:

> Save a note titled “Grok connection test” in my test channel: “Connected from Grok.”

Open Zas and verify the saved note. An item ID confirms delivery.

![Example request in the Grok message box, ready to send.](https://zas.red/media/ai-guide/grok-v1/prompt.webp)

## Files and permissions

Grok uses the same hosted connector and file limits as the other assistants. It receives 13 tools; the two ChatGPT attachment tools are omitted because they require ChatGPT file references. Images and PDF pages were readable in the Grok web test. Audio data arrived, but Grok could not interpret it in that conversation. A video download link does not mean Grok watched the video; media interpretation depends on the host.

For generated files, Grok must supply the original bytes through the inline or prepared-upload tools. If its environment cannot upload a file, save a note or upload the original in Zas. A filename or download URL alone does not send the file.

When a file cannot be read in the conversation, use the item's **Open in Zas** link. See [file limits and recovery](https://docs.zas.red/en/ai/troubleshooting.md).

## Grok Bot

Grok Bot in the browser can use this same connection. Listing channels, saving a note, and reading it back have been verified in browser Bot mode. The separate native Grok Bot app has not been tested with Zas.

Some Grok Bot sign-ins return through `https://www.cursor.com/agents/mcp/oauth/callback`. Zas accepts that exact callback as well as Grok web's `https://grok.com/connectors-oauth-exchange-code/`. Use the same Client ID, `zas-grok-web`, with Client Secret empty and **none (PKCE only)**.

If a previous connection attempt stopped at `invalid_request` before showing the Zas consent page, start **Connect** again in Grok to create a fresh sign-in request. Do not reuse the old authorization link or add a client secret. If it still fails, send Zas support the time, HTTP status and trace ID, without tokens or cookies.

[Manage or disconnect Grok](https://zas.red/ai/connect) · [Privacy and permissions](https://docs.zas.red/en/ai/privacy.md) · [Use your channels](https://docs.zas.red/en/ai/use-zas.md)


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