Run your company from the assistant you already use
Connect over MCP or a REST API and operate your org from ChatGPT, Claude, Cursor and more — with a scoped token that can only do what you can.
Secure MCP endpoint
One workspace URL your assistant connects to over MCP — you choose which agents and tools it can reach.
REST & webhooks
Prefer to build your own? Call your agents over a REST API and fire them from webhooks, with the same access controls.
Three steps to operate from your assistant
Create a connect token
In the app, open the Connect tab and generate a connect token. It acts as you — scoped to your role — so your assistant can only do what you can do.
Add the MCP server
Paste the server URL into your assistant — add it as an MCP server in Claude or Cursor, or as a GPT-Action in ChatGPT. Same token, either way.
Operate your org
Chat to your org from your assistant: check work in progress, ask for status, draft and approve actions. Everything still runs through your approvals and guardrails.
Add the MCP server
Create a connect token in the app, then point your assistant at it. The token acts as its owner — every action still runs through that person’s role and access rules.
ChatGPT uses the same token via GPT-Actions — one REST endpoint, no separate setup.
{
"mcpServers": {
"avantis": {
"url": "https://avantis-ai.com/mcp/<your-connect-token>"
}
}
}Replace <your-connect-token> with the token from the Connect tab.
Your assistant, your org
Claude
Add Avantis as an MCP server with your connect token URL.
ChatGPT
Verified via GPT-Actions — add Avantis as an action using your connect token.
Cursor
Drop the same MCP server config into Cursor and operate your org while you work.
Raycast
Add Avantis as an MCP server in Raycast and run your org straight from your launcher.
However you connect, the same rules, approvals and autonomy levels apply — access from outside is governed exactly like access from inside.
Operate from anywhere
Create a connect token and run your org from the assistant you already have open.