Connect OneLi to Grok

Add OneLi as a connector, sign in, and ask for Hebrew phone calls right from the chat.

In Grok you add OneLi as a Custom connector from its MCP address, then sign in to OneLi. Grok finds the tools on its own and uses them in chat.

The OneLi MCP address

https://mcp.oneli.io/mcp

Connect step by step

1/4

Who can use it

According to xAI, connectors are available to all Grok users on grok.com. On Grok Business an admin first adds the connector in console.x.ai, then each team member connects to it.

Use it in chat

In a grok.com chat, ask: “Use OneLi to call the salon and book a haircut for Thursday after 5 pm.” Grok calls the OneLi tool and brings the result back to the chat.

Build your own voice agent from the chat

Besides calls for you, the chat (Claude, ChatGPT, Grok or any MCP client) can build and manage your own voice agents, the same agents you build in the agent studio: create one from a template, show all its settings, change any of them, test it in a text conversation, and put it live or pause it. Every change shows up in the studio at once, and the other way round.

Create an agent

Describe the business and what the agent should do. The chat asks what is missing, creates the agent as a draft and shows all its settings:

In the chat

Create a voice agent for Danny's Pizza in Tel Aviv that answers incoming calls:
- Goal: take a complete order (what, how many, address and time)
- Opening: "Hi, you've reached Danny's Pizza! What would you like to order?"
- Menu: Margherita ₪49, Mushroom ₪55, delivery ₪15
- A male voice, short answers, and a Supervisor that checks prices against the menu

See every setting

Ask: “Show me all the settings of the pizza agent”. get_voice_agent returns everything, grouped like the studio’s pages: the agent (direction, goal, context, language, tone), opening, the conversation steps with the situations in each, the Supervisor, sections and rules, knowledge, tools and webhooks, variables, voice and brain, and call settings (time limits, turn-taking, hearing, memory and recording), plus what still blocks going live.

Change settings

Ask in words, for example “Add a step that asks for the address and time”, “Switch to a female voice and cap calls at 5 minutes” or “Make the agent speak English”. The chat reads the agent and sends update_voice_agent only what changes. Lists (steps, knowledge, rules) replace the whole list, so it also sends what stays, with its ids. It looks like this:

MCP

update_voice_agent {
  "agent_id": "va_…",
  "steps": [
    { "id": "st_…", "name": "Opening" },
    { "name": "The order", "ask": "What would you like to order?", "knowledge": ["Menu"],
      "situations": [{ "when": "They ask for something not on the menu", "do": "Say politely we don't have it and suggest something from the menu." }] },
    { "name": "Wrap-up", "say": "Thanks, your order is on its way!" }
  ],
  "supervisor": { "enabled": true, "instructions": "Make sure every price she says is from the menu.", "knowledge": ["Menu"] },
  "limits": { "max_s": 300, "wrap_at_s": 240 }
}

Test and go live

“Test the agent: call as a customer who wants two Margheritas to 10 Rothschild”. The chat plays the caller with test_voice_agent and shows you the replies. When you are happy, “Put the agent live” (deploy_voice_agent). The chat puts it live only after you confirm.

Manage everything: calls, knowledge and WhatsApp

The chat can also do everything the assistant on the site does: have the agent make an outbound call, read its calls and improve it, manage its knowledge bank, see every agent’s WhatsApp, read chats, send messages, and manage templates, rules and auto-reply. Before a call, a send or a delete it asks you.

These stay on the site, at oneli.io/app/agents: taking a phone number and paying, the agent’s contacts, recordings, connecting a WhatsApp number or an app (done in the browser), and the voice test. Connections made before this update get the new permissions automatically. In clients that keep a fixed copy of the tool list (ChatGPT, for example) press Refresh to see the new tools.

For developers

In the API and command-line tools you connect with a OneLi API key (oli_…) in a header. Create one at oneli.io/app/connect.

xAI API: a remote MCP tool

curl

curl https://api.x.ai/v1/responses \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $XAI_API_KEY" \
  -d '{
    "model": "grok-4.7",
    "input": [{ "role": "user", "content": "Use OneLi to verify the connection." }],
    "tools": [{
      "type": "mcp",
      "server_url": "https://mcp.oneli.io/mcp",
      "server_label": "oneli",
      "headers": { "Authorization": "Bearer oli_…" }
    }]
  }'

Grok Build (command line)

Terminal

# Sign in with OneLi in the browser on first use
grok mcp add --transport http oneli https://mcp.oneli.io/mcp

# Or with an API key
grok mcp add --transport http oneli https://mcp.oneli.io/mcp --header "Authorization: Bearer ${ONELI_API_KEY}"

Notes

The server must be reachable from the internet; mcp.oneli.io already is.
Adding a connector is documented on grok.com. xAI’s instructions do not describe it in the mobile apps.
In Grok Build (xAI’s command-line tool) you can also connect with an API key, see below.

Checked against the official docs on 25 October 2026:

Building your own agent? Connect OneLi to any framework →