- “What alerts fired for my top accounts this week?”
- “Draft a new-hire signal for VPs of Sales at Series B SaaS companies.”
- “Generate more leads for my champion-movement signal, then turn on daily monitoring.”
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 only sees the workspace 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 Plugins in the Codex app.
- 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
1
Open Plugins
In Codex, open Plugins.
2
Open MCP
Select MCP from the Plugins screen.
3
Add Avina
Click Add Avina, then follow the prompts to add the Avina MCP 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.
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 has access to the following tools, all scoped to your workspace:Read tools never modify your data. Write tools change signals in your workspace — your AI assistant will summarize what it’s about to do and may ask for confirmation before acting. New signals from
draft_signal are always created inactive so nothing goes live without your say-so.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.
- Workspace-scoped. Claude or Codex can only see and act on the workspace you’re a member of. If you belong to more than one, the connector uses the workspace tied to your session.
- Least privilege. Every request is authorized against your existing Avina role, and write tools funnel through a server-side allowlist — the assistant can only set the fields Avina explicitly permits.
- Revoke anytime. Remove Avina under 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:- Go to Organization settings → Connectors.
- Click Add, hover Custom, and choose Web.
- Enter the server URL
https://api.avina.io/mcpand click Add. - 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.