Meta · Connection guide

Muse & Muse Code

Connect Muse
to Love CRM.

Muse Code documents remote MCP servers and OAuth sign-in. The personal Muse app is a different product: a native custom-MCP setup path was not established in the official materials reviewed for this guide. Use the Muse Code instructions below, or confirm the personal app’s current connector support before connecting Love.

Documented setup: Muse Code. Personal Muse app: confirm connector compatibility for your version.

See setup steps Visit Muse

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. Confirm which Muse product you are using

    The configuration below is for Muse Code, Meta’s terminal coding agent. For the personal Muse app, check its official connection options rather than assuming the same settings exist.

  2. Add a remote server in Muse Code

    Merge the example into the mcp_servers block of your Muse Code settings file. Replace the placeholder with the address copied from Love’s API & MCP setup; preserve other server entries.

  3. Start OAuth sign-in

    Run muse mcp login love-crm and complete the browser authorization. Muse Code manages the resulting connection credentials.

  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.

Muse Code settings · then run muse mcp login love-crm
{
  "mcp_servers": {
    "love-crm": {
      "transport": "streamable_http",
      "url": "https://your-workspace.lovecrm.co/mcp",
      "enabled": true,
      "mode": "optional"
    }
  }
}

Client setup reviewed . Official Muse Code documentation

These instructions configure Muse Code, not a native Love plugin in the personal Muse app. A connector built for another product or provider still needs a compatible authorization flow.

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.

Use Muse Code to investigate permitted CRM records and prepare repeatable office workflows. A lawn care operator could review treatment-round context or prepare follow-up proposals without giving the client an Owner identity.

  • Identify the Love teammate connected to this session and show its assigned actions.
  • Review the lawn-service appointments this teammate can access and explain which records support your answer.

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.

Muse + Love

Your connection questions,
answered.

Can I paste Love’s MCP URL into the personal Muse app?

Confirm the personal app’s current connector support first. This guide does not establish a native custom-MCP menu for that app. Muse Code has a documented remote-MCP configuration and sign-in flow.

What happens if Love is temporarily unavailable in Muse Code?

The example uses Muse Code’s optional server mode so a connection problem need not stop the whole session. The agent should report unavailable CRM context rather than invent an answer.

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

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

OpenAI · Web · custom plugin

ChatGPT

Workspace MCP setup for ChatGPT.

Read connection guide