Anthropic · Connection guide

Terminal

Connect Claude Code
to Love CRM.

Claude Code can register Love’s remote HTTP MCP endpoint with claude mcp add. Authenticate from /mcp, complete Love’s Owner consent flow, and bind the connection to an active AI teammate. Start with discovery and permitted reads before proposing work.

HTTP MCP servers and OAuth are documented by Claude Code. Use an installed version with these features enabled.

See setup steps Visit Claude Code

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. Register the remote HTTP endpoint

    Replace the example workspace URL and run the command below. User scope makes the entry available across your Claude Code projects on that machine.

  2. Authenticate from Claude Code

    Run /mcp, select love-crm and follow the browser sign-in prompt. Keep the client’s OAuth flow intact.

  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.

Claude Code CLI · then authenticate using /mcp
claude mcp add --transport http --scope user love-crm https://your-workspace.lovecrm.co/mcp

Client setup reviewed . Official Claude Code documentation

User scope controls where the client configuration is available. It does not widen Love’s tenant, role or action permissions.

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.

Give the team building an operations workflow access to structured business context through the same API policy as the product. Useful starting points include understanding the tenant catalog and investigating a customer’s recurring service history.

  • Inspect the Love tenant catalog and explain the record types this teammate may use.
  • Find the records needed for a customer follow-up, then show a proposal for review without executing it.

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 Code + Love

Your connection questions,
answered.

Should the endpoint use HTTP or SSE mode?

Love’s hosted /mcp endpoint uses Streamable HTTP. Register it with Claude Code’s http transport rather than assuming it is a legacy /sse endpoint.

Can I share the MCP configuration with my team?

Claude Code supports project and user configuration scopes. A shared URL is not a shared authorization grant: each authorized connection still needs Love’s consent and teammate binding. Keep credentials out of the repository.

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 · Web & desktop

Claude

Workspace MCP setup for Claude.

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