OpenAI · Connection guide

Web · custom plugin

Connect ChatGPT
to Love CRM.

ChatGPT can use a remote MCP server through a custom plugin when account and workspace policies allow it. Add Love’s workspace /mcp URL, configure OAuth, and complete the Love consent flow for an active AI teammate. Select the resulting plugin in the conversation.

Custom MCP plugins depend on ChatGPT account and workspace permissions. This guide does not imply a public directory listing.

See setup steps Visit ChatGPT

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 ChatGPT Plugins

    Select the plus button and Add custom MCP server. Your account and workspace must allow custom MCP plugins.

  2. Describe the Love connection

    Enter a name and description, use your Love workspace MCP URL as the public HTTPS endpoint, and choose OAuth authentication. Review the discovered tools and the client’s connection prompts.

  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. Select the plugin and check access

    Finish creating and installing the plugin. In a new conversation, select it with @ and ask for the company, connected teammate and permitted tools before requesting any changes.

Client setup reviewed . Official ChatGPT documentation

A custom plugin connection is different from an OpenAI-approved marketplace listing. ChatGPT and Codex also have different setup surfaces; use the guide for your actual client.

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.

Ask business questions where you already work: understand an account, review upcoming service or prepare a follow-up for the office. Answers should identify the records used and stay within the teammate’s read permissions.

  • Using Love CRM, identify the connected teammate and the company it belongs to. Do not change records.
  • Review this customer’s permitted account context and explain the next follow-up the office should consider.

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.

ChatGPT + Love

Your connection questions,
answered.

Is Love already listed in the ChatGPT plugin directory?

This guide covers adding a custom MCP plugin using your workspace URL. It does not claim a public listing or platform endorsement.

Can I use a shared database or API key instead?

The hosted Love MCP connection requires its teammate authorization flow. Do not replace OAuth with a database credential, broad Owner token or shared AppSync key.

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

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