Connect Grok
Grok can use SimpleVox when you add it as a custom connector, a remote MCP server that signs in with OAuth. Grok then signs in with your own SimpleVox account, reaches only the numbers you allow, and can do only what you permit.
Before you start
Section titled “Before you start”- A SimpleVox account in a workspace, with access to at least one number.
- A Grok account that can add custom connectors. On Grok Business and Enterprise, a team admin may need to set up connectors first.
- The SimpleVox server address:
https://my.simplevox.app/mcp. It’s also on Settings → Integrations in SimpleVox, with a Copy button.
Add SimpleVox
Section titled “Add SimpleVox”-
In Grok on the web, open your connectors page at grok.com/connectors.
-
Choose New Connector, then Custom.
-
Enter the server URL
https://my.simplevox.app/mcp, and a name such as SimpleVox if Grok asks for one. -
If Grok asks how to sign in, choose OAuth. Leave any client ID and secret empty: SimpleVox registers the client automatically.
-
When Grok opens SimpleVox, sign in and check the consent screen: the workspace and email shown are yours, and the Redirect URI belongs to Grok or xAI.
-
Choose what it can do. Tick any permissions you want under Also allow it to, and choose All numbers you can access or Only the numbers I choose. Then choose Authorize. See Choose what each connection can do.
Grok Bot
Section titled “Grok Bot”Grok Bot, the agent that keeps working after you close the chat, can use the same server. Ask it to add a custom MCP server at https://my.simplevox.app/mcp, then complete the SimpleVox sign-in and consent screen when it opens. It doesn’t need a client ID: SimpleVox registers the client automatically. On the consent screen, the Redirect URI should belong to Grok, xAI or Cursor, which runs Grok Bot’s agents.
Grok Bot can run tools while you’re away. Choose its permissions with that in mind: start with read-only access, or add Mark conversations read, unread or done for inbox tasks. Before allowing texts, calls or contact changes, make sure it follows the shared confirmation rules.
Use it in a chat
Section titled “Use it in a chat”Ask Grok to use SimpleVox by name the first time:
Use SimpleVox. Which missed calls yesterday haven’t had a call or text back?
If you gave the connection more permissions, you can ask Grok to act too, such as “Add Mary’s new email address to her contact.” Before approving an action, read Control and safety. For call setup, see Assisted calls. For more ideas, see example prompts.
Building with the xAI API
Section titled “Building with the xAI API”If you call Grok through the xAI API, you can give it SimpleVox as a remote MCP tool by passing the server URL and a bearer token. That token has to be a SimpleVox OAuth access token for the person, which your app gets through the delegated OAuth flow with an HTTPS callback address. Personal API tokens don’t work with MCP. OAuth access tokens expire after 15 minutes, so your app has to refresh them.
The xAI API runs MCP tools without asking a person first. Implement the shared confirmation and retry rules before enabling writes, or leave those permissions off.
For account setup, missing numbers, permissions, texting or calling problems, see AI tools troubleshooting.
Disconnect
Section titled “Disconnect”Remove SimpleVox from your Grok connectors, or choose Disconnect next to it on Settings → Integrations in SimpleVox. Disconnecting in SimpleVox stops access straight away.