Add Ava as a tool in a Microsoft Copilot Studio agent so your team can ask Ava about their Spaces without leaving Copilot. Ava answers using each person's own Ava account and permissions, the same as in the Ava web app.

This setup has a hand-off in the middle. After you add the Ava server (Step 5), Copilot Studio shows a Redirect URL that is unique to your environment. Vivun must register that URL before anyone can sign in. Send it to your Vivun Technical Account Manager or Vivun Support, and wait for confirmation before continuing to Step 6. Signing in before the URL is registered fails with a redirect_uri mismatch error.

Before You Start

A Copilot Studio maker role for the agent you want to add Ava to.
A Client ID and Client secret from Vivun. Request these from your Vivun Technical Account Manager or Vivun Support.
Ava accounts for your users. Each person signs in with their existing Ava credentials.

Connection Values

Server URL: https://mcp.ava.vivun.com/mcp
Authorization URL: https://mcp.ava.vivun.com/oauth/authorize
Token URL: https://vivun-ava-prod.us.auth0.com/oauth/token
Refresh token URL: https://vivun-ava-prod.us.auth0.com/oauth/token
Scopes: mcp:read:spaces mcp:consult:agent mcp:write:spaces offline_access

Add Ava to Your Copilot Studio Agent

In Copilot Studio, open your agent and go to Tools (or Actions). Click Add a tool → Model Context Protocol → Add MCP server.
Fill in the server details:
- Server name: Ava
- Server description: List your Ava Spaces and ask Ava questions about them
- Server URL: https://mcp.ava.vivun.com/mcp
Under Authentication, choose OAuth 2.0. Under Configuration type, choose Manual.
Don't choose Dynamic or Dynamic (with discovery). With those options, sign-in appears to work but every request to Ava fails afterward.
Fill in the OAuth fields:
- Client ID: the value Vivun gave you
- Client secret: the value Vivun gave you
- Authorization URL: https://mcp.ava.vivun.com/oauth/authorize
- Token URL: https://vivun-ava-prod.us.auth0.com/oauth/token
- Refresh token URL: https://vivun-ava-prod.us.auth0.com/oauth/token
- Scopes: mcp:read:spaces mcp:consult:agent offline_access
Separate the scopes with spaces, not commas. The Authorization URL must point to mcp.ava.vivun.com, not to the token URL's address. mcp:write:spaces is what lets Copilot add a Space for a user. Leave it out and everything else still works, but adding a Space is refused.
Click Create. Copilot Studio shows a Redirect URL for the connection. It usually starts with https://global.consent.azure-apim.net/redirect/.
Stop here. Copy the Redirect URL exactly as shown and send it to your Vivun Technical Account Manager or Vivun Support. Don't click Sign in until Vivun confirms the URL is registered. Each Copilot Studio environment has its own Redirect URL, so send one for each environment you set up.
After Vivun confirms, click Sign in (or Create a new connection). Sign in with your Ava account in the window that opens, and approve the requested access.
Back in Copilot Studio, confirm mcp:write:spaces is what lets Copilot add a Space for a user. Leave it out and everything else still works, but adding a Space is refused.

Verify the Connection

In the agent's Test pane, ask "List my Ava spaces." The agent should return the Spaces the signed-in user can see in Ava. Then ask a question about one of them, such as "Ask Ava what the latest is on the Acme Space." Then ask 'Find the Acme account in Salesforce and add it as a Space.' as an optional check.

What the Connection Allows

Copilot acts only as the signed-in user, with these capabilities:

Read Spaces (list_spaces): see the Ava Spaces the user has access to, and whether each one's data is still loading or ready.
Read deals and product gaps (list_deals, list_product_gaps): read the user's open deals and the product gaps Ava has recorded for their Spaces.
Search accounts (search_salesforce_accounts): search the user's Salesforce accounts and see which already have a Space.
Consult Ava (ask_agent): ask Ava a question about one Space and get its answer.
Add a Space (create_space): when the user asks or confirms, add a Salesforce account's Space to their list. Needs the mcp:write:spaces scope.

Copilot can't see anything the user couldn't see in Ava directly. For more on what you can ask and how consultations work, see Connect AI Assistants to Ava (MCP).

Troubleshooting

"redirect_uri mismatch" or "Callback URL mismatch" in the sign-in window: Vivun hasn't registered your Redirect URL yet, or it was sent with a typo. Copy it again from Copilot Studio and resend it to Vivun.
Sign-in succeeds, but every request to Ava fails: check that the Authorization URL is exactly https://mcp.ava.vivun.com/oauth/authorize and that the configuration type is Manual.
The sign-in window never opens, or you see "invalid_client": the Client ID or Client secret was pasted incorrectly. Copy both again from the values Vivun supplied.
A request is blocked with a 403 error: contact Vivun Support and include the approximate time it happened.
Already connected before new permissions were added: Reconnecting alone does not grant the new permission in Copilot Studio, because the connector only asks for the scopes typed into it. For example, if you need the write to spaces permission, edit the connector, add mcp:write:spaces to its Scopes, save, and then have each user sign in to the connection again and approve the new access.
Adding a Space is refused or says permission is missing. The connector's scopes don't include mcp:write:spaces, or the user hasn't signed in again since it was added. See bullet above.

Need help? Contact your Vivun Technical Account Manager or Vivun Support.

Connect Ava to Microsoft Copilot Studio