Connect Ava to Slack so your team can ask Ava questions directly from Slack. Ava answers using each person's own Ava account and permissions, the same as in the Ava web app.

This connection is set up once by a Slack administrator, using a Slack app in your workspace. After that, each user connects their own Ava account in a few clicks.

How this differs from the Ava Slack integration: The Slack Integration (Org Level) connects Slack channels to your Spaces as a source of knowledge. This article covers something separate: asking Ava questions from Slackbot. You can use either one, or both.

Overview

Administrator, once: create or choose a Slack app, add the Ava server, add the audience in the app manifest, install the app, and approve it if your workspace requires approval.
Each user, once: connect to Ava from Slackbot, then start asking questions.

Before You Start

Permission to create and install Slack apps. In most workspaces, this means a Workspace Owner or Admin.
MCP Servers available on your Slack plan. If MCP Servers does not appear under Features in your Slack app's settings, contact Slack about your plan.
Ava accounts for your users. Each person signs in with their existing Ava credentials the first time they use Ava from Slack.

Connection Values

You'll use these values in the steps below. Copy them exactly, including the trailing slash on the audience.

Ava server URL: https://mcp.ava.vivun.com/mcp
Client ID: https://slack.com/.well-known/oauth-client-metadata
Client Secret: none, leave blank
Authorization URL: https://vivun-ava-prod.us.auth0.com/authorize
Token request URL: https://vivun-ava-prod.us.auth0.com/oauth/token
OAuth scopes: mcp:read:spaces, mcp:consult:agent, offline_access
Audience: https://mcp.ava.vivun.com/

Administrator Setup

Step 1: Create or Choose a Slack App

If you don't have a Slack app for Slackbot connections yet:

Go to api.slack.com/apps and click Create New App.
Choose From scratch.
Enter a name such as Ava, choose the workspace where you want Ava available, and click Create App.

If you already have one: open it from api.slack.com/apps and continue to Step 2.

Step 2: Add the Ava Server

In the left sidebar, under Features, click MCP Servers.
Click Get Started or Add MCP Server.
Fill in the form:
- Name: Ava (users see this name; any name works)
- URL: https://mcp.ava.vivun.com/mcp
- Auth type: Manual OAuth
- Client ID: https://slack.com/.well-known/oauth-client-metadata
- Client Secret: leave blank
- Authorization URL: https://vivun-ava-prod.us.auth0.com/authorize
- Token request URL: https://vivun-ava-prod.us.auth0.com/oauth/token
- Use HTTP Basic Authentication: unchecked
- Use PKCE (Proof Key for Code Exchange): checked
- OAuth scopes: mcp:read:spaces, mcp:consult:agent, offline_access. Press Enter after each one.
- Identity URL and the fields below it: leave blank
Click Save.

Step 3: Add the Audience in the App Manifest

The form in Step 2 has no field for the audience Ava requires, so you add it to the app manifest once.

In the left sidebar, click App Manifest and switch the editor to JSON.
Find the external_auth_providers section. It contains one provider that Slack created from the form in Step 2, with a key that starts with mcp_.
Inside that provider's options object, add the block below. Place it after "token_url", and make sure the line before it ends with a comma.
```
"authorization_url_extras": {
    "audience": "https://mcp.ava.vivun.com/"
}
```
Click Save Changes.

After the change, the provider looks like this:

"external_auth_providers": {
    "oauth2": {
        "mcp_ava": {
            "provider_type": "CUSTOM",
            "options": {
                "client_id": "https://slack.com/.well-known/oauth-client-metadata",
                "scope": [
                    "mcp:read:spaces",
                    "mcp:consult:agent",
                    "offline_access"
                ],
                "provider_name": "Ava",
                "authorization_url": "https://vivun-ava-prod.us.auth0.com/authorize",
                "token_url": "https://vivun-ava-prod.us.auth0.com/oauth/token",
                "authorization_url_extras": {
                    "audience": "https://mcp.ava.vivun.com/"
                },
                "use_pkce": true,
                "token_url_config": {
                    "use_basic_auth_scheme": false
                }
            }
        }
    }
}

Note: Your provider key and provider_name may differ from mcp_ava and Ava, depending on what you entered in the form. Leave them as Slack generated them.

While you're in the manifest, confirm that oauth_config.scopes.bot contains "mcp:connect". Slack adds it when you save the form in Step 2. If it's missing, add it.

Step 4: Install and Approve the App

Install

In the left sidebar, click Install App, or Reinstall App if the app was installed before you made these changes.
Review the permissions and click Allow.

In Enterprise Grid organizations, install the app at the org level to make it available across workspaces.

Approve (if your workspace requires app approval)

Open slack.com/apps/manage and go to the Requests queue.
Open the request for the app. In the Connected MCP Servers section, check Allow next to Ava.
Approve the app.

Installed connections then appear under Integrations → Installed apps in the Slack admin dashboard.

Verify the Connection

Under Features → MCP Servers, open the menu next to Ava, choose Tools, then click Fetch Tools. If the connection is set up correctly, Slack lists Ava's tools.

Connect Your Ava Account (All Users)

Once your administrator has finished the setup above, each user connects once:

In Slack, open a direct message with Slackbot.
Click the Apps button in the message toolbar.
Find Ava and click +.
A browser window opens on the Ava sign-in page. Sign in the same way you sign in to the Ava web app.
Approve the request to let Slack read your Spaces and consult Ava on your behalf.
Back in Slack, Ava now appears under Your apps.

Ask Ava

Ask Slackbot in plain language. For example:

"What tools are available from Ava?"
"Ask Ava what changed on the Acme account this week."

The first time Slackbot uses Ava for you, it asks you to confirm with Allow once, Always allow, or Deny. You can change these choices at any time with the Manage button next to Ava under Your apps.

What the Connection Allows

Slack acts only as the signed-in user, with two capabilities:

Read Spaces: see the list of Ava Spaces you have access to.
Consult Ava: ask Ava questions and get answers based on your own accounts and data.

Slack can't see anything you couldn't see in Ava directly.

Need help? Contact Vivun Support.

Connect Ava to Slackbot