Cursor · Connection guide

Editor & agent

Connect Cursor
to Love CRM.

Cursor supports remote MCP servers with OAuth. Add Love’s workspace MCP URL to mcp.json or the supported MCP settings, authenticate, and choose the Love AI teammate that should represent the connection. The URL identifies the server; authorization determines access.

Streamable HTTP and OAuth are documented in Cursor’s MCP guide. Team policy can limit available servers.

See setup steps Visit Cursor

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. Add the remote server entry

    Merge the example into ~/.cursor/mcp.json for your user, or .cursor/mcp.json for a project. Replace the workspace address and preserve existing server entries.

  2. Enable Love and sign in

    Open Cursor’s Customize / MCP controls, find love-crm and follow the OAuth authentication prompt for the remote server.

  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.

Cursor · mcp.json
{
  "mcpServers": {
    "love-crm": {
      "url": "https://your-workspace.lovecrm.co/mcp"
    }
  }
}

Client setup reviewed . Official Cursor documentation

An MCP server in a shared project is discoverable to collaborators. Keep the example URL public-only and let each person complete an approved OAuth connection.

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 CRM discovery next to the tools your team already builds with. Ask about customer relationships, appointment schemas or available catalog actions, then design workflows around the returned contracts.

  • List the CRM entity schemas this Love teammate can discover and explain their relationships.
  • Show the assigned catalog actions for this teammate and identify which one fits a service follow-up.

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.

Cursor + Love

Your connection questions,
answered.

Is the workspace URL itself a secret?

The public /mcp address is not an access token. Love still requires a valid authorization flow. Never add tokens, passwords or private credential parameters to the URL.

Does Cursor’s tool approval replace Love permissions?

No. Client-side approvals and tool filters are an additional control. Love checks the bound teammate’s permissions on the server, and catalog action proposals follow Love’s review workflow.

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

Anthropic · Terminal

Claude Code

Workspace MCP setup for Claude Code.

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