OpenAI · Connection guide

Desktop, CLI & IDE

Connect Codex
to Love CRM.

Codex supports remote MCP over Streamable HTTP with OAuth. Add Love’s workspace MCP URL, run the client’s sign-in flow, and authorize one active Love AI teammate. Codex receives that teammate’s permitted tool surface and can use structured CRM context in its work.

Remote HTTP and OAuth are documented for Codex hosts. Workspace policy and your installed client still apply.

See setup steps Visit Codex

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. Copy the workspace address from Love

    Open API & MCP setup and copy your company’s public HTTPS MCP URL. Replace the example address in the commands below.

  2. Register Love in Codex

    Run codex mcp add with the workspace URL. Codex stores MCP server configuration on its host; client surfaces on the same host can share it.

  3. Authenticate the remote server

    Run codex mcp login love-crm. Let Codex manage OAuth discovery and its callback; follow the browser flow instead of constructing a consent URL yourself.

  4. 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.

  5. 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.

Codex CLI · replace the example workspace
codex mcp add love-crm --url https://your-workspace.lovecrm.co/mcp
codex mcp login love-crm

Client setup reviewed . Official Codex documentation

This is Love’s hosted teammate connection. Running a developer stdio server from a source checkout is a separate setup with different credentials and should not be substituted for tenant OAuth.

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.

Pair a coding and operations agent with the actual book of business. Investigate an account, explain a recurring-service workflow, or prepare an approved action from structured customer and scheduling context.

  • Use Love’s discovery tools to explain the customer and appointment data available to this teammate.
  • Read this customer’s permitted service history and prepare the next follow-up for human review.

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.

Codex + Love

Your connection questions,
answered.

Do I need to give Codex Love’s database credentials?

No. The hosted setup uses Love’s OAuth connection and a bound AI teammate. Do not put database credentials, an AppSync API key or an Owner token into a chat or a committed configuration file.

Does Codex get my Owner permissions after I sign in?

The Owner authorizes the connection, but the remote client is bound to the selected AI teammate. Love rejects an Owner acting role for that teammate connection and checks the teammate’s permissions on the API side.

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

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

OpenAI · Web · custom plugin

ChatGPT

Workspace MCP setup for ChatGPT.

Read connection guide