Skip to main content
Avina exposes a hosted Model Context Protocol (MCP) server so you can ask Claude or Codex to work with your Avina workspace in natural language: look up accounts, contacts, and leads, build and monitor audiences, set up automations, write AI Sequences, and more. Once connected, you can ask your AI assistant things like:
  • “What leads came in for my top accounts this week?”
  • “Draft a new-hire audience for VPs of Sales at Series B SaaS companies, then turn on daily monitoring.”
  • “Find decision-makers for this week’s leads that don’t have a contact yet.”
  • “Create an automation that enrolls A and B fit web visitors into my pricing-page sequence.”
  • “Write a three-step AI Sequence for my champion-movement audience and preview it for Acme.”
Endpoint: https://api.avina.io/mcp · Transport: Streamable HTTP · Auth: OAuth (Avina / WorkOS login — no API keys to copy)
You sign in with your normal Avina login. Claude or Codex can only see and act on workspaces you’re a member of.

Before you start

  • An active Avina workspace and login. If you can sign in at app.avina.io, you’re set.
  • For Codex: access to MCP settings in the Codex app. Avina isn’t a bundled plugin — you add it yourself as a custom MCP server using the URL below.
  • For Claude: a plan that supports custom connectors — Free, Pro, Max, Team, and Enterprise all qualify. On Team / Enterprise, custom connectors may be gated by your workspace owner.

Connect in Codex

Avina isn’t part of the Codex plugin catalog — you add it manually as a remote MCP server, the same way you would in Claude.
1

Open MCP settings

In Codex, go to Settings → Plugins → MCP.
2

Add an MCP server

Click Add MCP server and choose Streamable HTTP as the transport.
3

Enter the Avina MCP URL

Fill in the server details:Leave any authentication / client-credential fields blank — Avina handles the OAuth handshake automatically. Save the server.
4

Sign in to Avina

Complete the Avina / WorkOS login in your browser and approve access. When you return to Codex, Avina is ready to use.
Start a task and ask Codex to use Avina, for example: “Using Avina, show me the highest-fit accounts with signals this week.”

Connect on claude.ai

1

Open Connectors

Go to Settings → Connectors (also reachable via Customize → Connectors).
2

Add a custom connector

Click Add custom connector.
3

Enter the Avina MCP URL

Paste the server URL and give it a name:Leave the Advanced settings (OAuth Client ID / Secret) blank — Avina handles the OAuth handshake automatically. Click Add.
4

Sign in to Avina

Click Connect on the new Avina connector. A browser window opens for your Avina / WorkOS login. Approve access, and you’ll be returned to Claude with the connector marked Connected.
5

Enable it in a chat

In any conversation, click the + button, choose Connectors, and toggle Avina on. Claude can now call your workspace.

Connect in Claude Cowork

Claude Cowork uses the same custom-connector system as claude.ai.
1

Open Connectors

In Cowork, open Settings → Connectors.
2

Add the Avina connector

Choose Add custom connector, then enter:Click Add, then Connect and complete the Avina login in your browser.
3

Use it

Reference the connector in your task, e.g. “Using Avina, list this week’s champion-movement alerts and draft outreach for the top three.” Cowork will call the tools it needs and ask before running any action that changes your data.

What Claude and Codex can do

Once connected, Claude or Codex can use the following tools. Read tools never change anything. Write tools change your workspace.
The assistant may say “signal” where the Avina app says “audience”. A signal in these tools is the same thing as an audience in the app, and a signal’s alerts are its leads.

Orientation

Accounts, contacts, and leads

Audiences

Workspace settings and personas

Automations

AI Sequences

Saved Documents

Suppression list

Available when your workspace includes a suppression list.

Safe by default

  • New things start off. Audiences from draft_signal are created inactive, automations are created paused, and AI Sequences are created unpublished, so nothing goes live until you say so.
  • Going live is confirmed. Before activating an automation, publishing a sequence, or enrolling leads (which can send real outreach), the assistant checks with you.
  • Deletes are two-step. Deleting a persona or a Saved Document needs an explicit confirmation.
  • Retries don’t duplicate. Enrolling the same leads twice doesn’t enroll them twice.

What it can’t do yet

The integration can’t send one-off emails, edit or delete accounts, contacts, or CRM data, delete audiences or automations, manage users or billing, export data, or work with sequence templates. For those, use the Avina dashboard. Persona contact countries (limiting a persona’s contacts to people located in certain countries) can’t be set in the dashboard yet. Set them through this integration or the Avina API.

Security & access

  • You sign in as you. Authentication runs through Avina’s standard WorkOS login (OAuth 2.0). No API keys or secrets are pasted into your AI assistant or stored in a config file.
  • Scoped to your workspaces. Claude or Codex can only see and act on workspaces you’re a member of, including sub-workspaces you administer through a parent workspace, with the same permissions you have in Avina.
  • Multiple workspaces. If you belong to more than one workspace, the assistant asks which one to use (or uses the one you named earlier in the conversation) and tells you which workspace it used. Ask it to “use the Acme workspace” to switch.
  • Least privilege. Write tools go through a server-side allowlist, so the assistant can only change the fields Avina explicitly permits.
  • Revoke anytime. Remove the Avina server under Settings → Plugins → MCP in Codex, or disconnect it under Settings → Connectors in Claude, to immediately cut off access.

Team & Enterprise workspaces

On Team and Enterprise plans, a workspace owner adds the connector once so members can enable it:
  1. Go to Organization settings → Connectors.
  2. Click Add, hover Custom, and choose Web.
  3. Enter the server URL https://api.avina.io/mcp and click Add.
  4. Members then open Settings → Connectors and click Connect on the Avina connector to sign in with their own Avina login.

Troubleshooting

Still stuck? Email support@avina.io and we’ll help you get connected.