AVAY

Connecting your own tools

Letting AVAY reach the systems your team already works in.

Out of the box AVAY knows about your meetings and the web. Connectors let it reach further — a ticket tracker, a wiki, a customer record — so that “what did we promise them in March” can be answered from the system that actually holds the answer.

A connector is an MCP server: a small service that describes what it can do and exposes a handful of tools. Anything speaking that protocol works here; there is no list of blessed integrations.

Adding one

  1. Open Tools from the menu under your account picture, at the foot of the rail.
  2. Give it a name you will recognise in a meeting — “Company Jira”, not “mcp-prod-2”. The name is what AVAY says out loud when it uses the tool.
  3. Paste the server's address.
  4. If it needs a token, paste that too. If it uses OAuth, leave it blank and choose Connect with OAuth instead.
  5. Choose Add and test. AVAY connects, asks the server what it can do, and lists the tools it found.
  1. You add the addressNothing is trusted yet; the server has only been named.
  2. AVAY asks what it offersThe server returns its own list of tools and descriptions.
  3. You authorise itA token you paste, or an OAuth round trip you approve in your browser.
  4. It becomes availableIn your meetings, and only in yours, until you switch it off.

Who can use a connector

The account that added itCredentials belong to you. Nobody else can see them, and they are never sent back to a browser once saved.
Meetings you hostAVAY uses the connectors of whoever owns the meeting — not of whoever happens to be asking. A guest cannot reach your systems by asking AVAY a clever question.
Per meetingA host can switch any connector off for a single meeting without removing it. Useful when the call has people from outside in it.

More in AVAY, the assistant

More on this

Try it

Open avay.ai and start a meeting — nothing to install, and the people you invite do not need accounts. See what it costs.