Anthropic · Connection guide

Web & desktop

Connect Claude
to Love CRM.

Claude supports custom remote MCP connectors on eligible accounts. Add your Love workspace MCP URL as a connector, keep OAuth sign-in enabled, and choose an active Love AI teammate during consent. Enable the connector in the conversation where you want to use it.

Custom connector availability and administrator requirements depend on the Claude plan and organization policy.

See setup steps Visit Claude

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. Open Claude’s connector settings

    On an eligible individual account, open Customize → Connectors and add a custom connector. Team and Enterprise users may need an organization Owner to add it first.

  2. Add Love CRM and its MCP address

    Name the connector Love CRM, enter the workspace URL copied from Love, and review the detected OAuth settings. Keep sign-in enabled and use a supported client registration option.

  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. Enable it in your conversation

    Connect the connector, then enable Love CRM for the conversation. Start with the read-only connection check below.

Client setup reviewed . Official Claude documentation

A custom connector is not an Anthropic-certified Love integration. Organization policy and the selected Love teammate both govern what can be accessed.

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.

Bring recurring account questions into a conversation: explain service history, investigate a billing question, or prepare an office follow-up with the relevant customer context in view.

  • Which Love company and AI teammate is connected? List the permitted actions without changing any records.
  • Explain this customer’s recent service and open invoices using only the records this teammate can access.

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.

Claude + Love

Your connection questions,
answered.

Do I need a manual OAuth client ID for Claude?

Love’s hosted server supports automatic client registration and published client metadata. Follow the OAuth options your Claude version offers; do not substitute a shared API key for the teammate sign-in flow.

Why does Claude say the connector is installed but not usable?

Check that the account has authenticated, that the connector is enabled in the current conversation, and that the chosen Love teammate is active and has the required read permissions.

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.

xAI · Personal agent

Grok Bot

Workspace MCP setup for Grok Bot.

Read connection guide

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 · 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