Pest control
Understand recurring service, customer history and upcoming appointments before preparing a follow-up.
Bring your own agent · Keep your own rules
Your agent.
Your business.
Your boundaries.
Connect the assistant you already use to the work your business runs on. Love’s MCP server gives compatible agents structured CRM context through a permission-scoped AI teammate.
For enabled early-access workspaces. Client support and workspace policies apply.
How access works
Your Owner signs inAuthorize the connection in Love
One AI teammate is selectedA defined role and assigned actions
Love checks each requestYour tenant. Your permission boundary.
Connection library
The agent you prefer.
The context it needs.
Choose your client for setup instructions, useful first questions, and the permission details that matter. These are custom MCP connection guides, not claims of a vendor-certified integration.
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 guideAnthropic · 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 guideOpenAI · Web · custom plugin
ChatGPT
Workspace MCP setup for ChatGPT.
Read connection guideThird-party names and logos identify their products. Each guide links to the provider’s official documentation. Muse Code and the personal Muse app have different connection options.
One workspace address
A URL starts the connection.
A teammate defines the access.
MCP stands for Model Context Protocol: a standard way for an AI client to discover tools and exchange structured information. Love exposes that interface at your company’s /mcp endpoint.
An employee’s personal AI client does not become an administrator by knowing the address. An Owner authorizes the connection to a specific active teammate, and Love checks that teammate’s role and capabilities.
Explore Love’s agent-native architectureWorkspace endpoint
https://your-workspace.lovecrm.co/mcpExample address. Copy your exact URL from Love’s API & MCP setup.
- Transport
- Streamable HTTP
- Sign-in
- OAuth with PKCE
- Identity
- One active AI teammate
From context to useful work
Built around the way
home services run.
Start with the records your teammate can read. Then identify the right catalog action before proposing a change.
Lawn care
Investigate treatment-round questions and service timing with customer and property context.
Office operations
Explain a billing question or prepare the next customer response with the underlying records in view.
Clear answers
Before you connect.
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.