xAI · Connection guide

Personal agent

Connect Grok Bot
to Love CRM.

Grok Bot can add a remote MCP server by URL. In an enabled Love workspace, provide your company’s MCP address, complete Love’s browser sign-in, and bind the connection to one active AI teammate. Grok Bot can then use the tools that teammate is permitted to access.

Remote MCP by URL is documented by Grok Bot. Your account and team policies must permit the connection.

See setup steps Visit Grok Bot

Setup · Hosted MCP

From your workspace
to your agent.

Before starting, have an enabled Love workspace, Owner authorization and an active AI teammate with the right permissions for the work. The example URL is a placeholder; copy the actual address from Love’s API & MCP setup.

  1. Get your company’s MCP address

    In Love’s API & MCP setup, copy the HTTPS address ending in /mcp. Use the exact workspace address, not the marketing website.

  2. Ask Grok Bot to add Love CRM

    Give Grok Bot the public MCP URL and ask it to add a remote MCP connection named Love CRM using OAuth. Follow its connection card to authenticate. Team connector policy may require an administrator.

  3. Choose the teammate in Love

    Follow the browser sign-in, authenticate as a Love Owner, and select an active AI teammate. Review its role, capabilities and assigned actions before consenting. The connection uses that teammate’s identity, rather than inheriting your Owner access.

  4. Check the connection before doing work

    Ask the agent to identify the company and bound teammate, list permitted tools and assigned actions, and perform a read-only lookup. Confirm the result before requesting a business action.

Client setup reviewed . Official Grok Bot documentation

Grok Bot app connections can be shared across your Bots within the same account. Choose the Love teammate accordingly; the connection should not be treated as private to one named Bot.

Make the first request
a connection check.

Use this read-only prompt before delegating work. A successful sign-in should identify the right company and teammate, not just show a connected icon.

Read-only connection check
Identify the Love company and AI teammate connected to this session.
Call get_mcp_connection and get_bound_teammate.
Use list_catalog_actions with the assigned scope, then inspect get_tenant_catalog.
Summarize the permissions and action types you actually received.
Do not submit proposals, apply routes, send messages, change records or collect payments.

Useful questions
to ask next.

Keep a persistent assistant close to the office work: recurring customer questions, service follow-ups and the next day’s planning. Love supplies the business context and permission boundary; Grok Bot provides the conversation.

  • Show the recurring customers with upcoming appointments that my Love teammate is allowed to read.
  • Prepare a service follow-up proposal for my review. Show the customer context before proposing anything.

Use only the tools actually returned for the connected teammate. For a catalog business action, ask for a proposal and review it in Love’s Home workspace. Routing collaboration follows its own workflow-specific permissions and apply controls.

Grok Bot + Love

Your connection questions,
answered.

Is Grok Bot the same connection as the Grok API?

No. This guide covers adding Love as a remote MCP connection in Grok Bot. Building an application with the Grok API is a separate integration and authentication project.

Can each employee use a personal Grok Bot?

A personal client does not grant itself Love access. A Love Owner must authorize a connection to an active AI teammate. Use separate connections and appropriately limited teammates for different responsibilities, and review the client’s own account-sharing rules.

Can I connect an AI client that is not listed here?

A compatible client needs remote Streamable HTTP MCP and Love’s OAuth authorization flow. Add the exact workspace URL, authorize an active AI teammate, and start with read-only discovery. Support for local MCP servers or API keys alone does not establish compatibility. Confirm your client’s current documentation and workspace policy before using it.

What is Love CRM’s MCP address?

Use the exact URL in your workspace’s API & MCP setup. The address follows https://your-workspace.lovecrm.co/mcp; replace your-workspace with the provisioned workspace hostname. A public URL identifies the endpoint but does not authorize access.

Does connecting an agent expose my whole business?

The hosted connection is bound to a selected active AI teammate in one tenant. Its role permissions and assigned actions limit what it can use. Review that role carefully: broad read permissions can still expose broad business context to the external agent provider.

Can the connected agent grant itself more permissions?

The teammate connection cannot use an Owner acting role, change users or teammate governance, or approve its own catalog action proposals. Love applies the permission checks in its API, beyond instructions supplied to the model.

What requires human approval?

Business actions submitted through Love’s catalog proposal path wait for review in Home. Workflow-specific tools, including routing collaboration, have their own capabilities and execution paths. Review those separately; a connection is not a blanket promise that every tool uses the same approval process.

How do I stop a connection?

Revoke the connection’s authorization or deactivate its bound Love teammate. Love rechecks the teammate and connection state on subsequent requests. Removing a client configuration alone is different from revoking its server-side authorization.

Is setup available to every Love account?

Love is in early access. Use these guides with an enabled workspace, an active teammate and a compatible client. Confirm tenant availability and client-specific support with Love before treating a connection as ready for your business.

See Love with your agent

More ways to work

One business.
Your choice of agent.

Meta · Muse & Muse Code

Muse

Muse Code setup and personal Muse compatibility.

Read connection guide

OpenAI · Desktop, CLI & IDE

Codex

Workspace MCP setup for Codex.

Read connection guide

Anthropic · Web & desktop

Claude

Workspace MCP setup for Claude.

Read connection guide

Anthropic · Terminal

Claude Code

Workspace MCP setup for Claude Code.

Read connection guide

Cursor · Editor & agent

Cursor

Workspace MCP setup for Cursor.

Read connection guide

Google · Terminal

Gemini CLI

Workspace MCP setup for Gemini CLI.

Read connection guide

OpenAI · Web · custom plugin

ChatGPT

Workspace MCP setup for ChatGPT.

Read connection guide