Owlbound
Browse the docs

Guide 11

Connect Grok

Add Owlbound as a custom connector in Grok and sign in with your Owlbound account, or use a key from the xAI API.

Last updated from API version 2026-10-06 at (live spec, refreshed hourly). openapi.json

Use Owlbound from Grok: read your contacts, companies, tables and sequences, prepare enrichments and sends, and check their progress. Grok connects to the Owlbound MCP server and signs in with your Owlbound account. You need no API key and no client secret.

Before you start

  • A Grok plan that includes custom connectors.
  • On Grok Business or Enterprise, a team admin may have to add the connector first in the xAI console. Then members only sign in.
  • An Owlbound account in the workspace you want Grok to use.

Add the connector

  1. Open grok.com/connectors.
  2. Click New Connector, then Custom.
  3. Fill in the form: name it Owlbound, paste the server URL below, and choose OAuth as the authentication. Leave the client ID and secret empty if the form shows them: Grok finds the Owlbound sign in on its own.
  4. Save. Grok opens an Owlbound window.
  5. Sign in to Owlbound if asked, pick the workspace, review what Grok may do (read, enrich, write, act) and click Allow.
  6. Back in Grok, turn the Owlbound connector on in a chat and ask, for example, “List my 10 newest contacts in Owlbound”.
Server URL
https://app.owlbound.ai/api/v1/mcp

What Grok can and cannot do

  • Grok acts as you, in the workspace you picked, with at most your role's rights and the scopes you allowed.
  • Every action tool runs a dry run first, so you see the plan, the targets and the credits before anything runs.
  • Sends (LinkedIn, email, CRM) are never sent by Grok. They wait for a person in Approvals in the Owlbound app, and Grok gives you the link. See how actions work.

Disconnect

In Owlbound, open Settings > Connected apps and click Disconnect next to Grok. Grok loses access at once. You can also remove the connector in Grok.

Troubleshooting

  • “This redirect URI is not allowed”: Grok used a callback address Owlbound does not know. Contact support with the address shown.
  • Grok asks you to sign in again: your connection was disconnected or you left the workspace. Sign in again from the connector.
  • The server URL is refused: use exactly https://app.owlbound.ai/api/v1/mcp (https, no trailing slash).

Using Owlbound from the xAI API

The remote MCP tool of the xAI API takes a fixed token instead of a sign in. Use an Owlbound API key from Settings > Settings > Workspace > Developer:

json
{
  "type": "mcp",
  "server_url": "https://app.owlbound.ai/api/v1/mcp",
  "server_label": "owlbound",
  "authorization": "owl_sk_..."
}

Keep the key on your server. The key's scopes and daily caps limit what the model can do.

MCP clients and protocolConnect any MCP client with sign in or an API key, and how the server speaks MCP.Connect Gemini EnterpriseCreate an OAuth app in Owlbound, add it as a custom MCP server in Google Cloud, and let each person sign in.