Checked against support.claude.com on 30 August 2026
Lovie

Lovie MCP›Claude

Chat app

Claude

Claude calls a remote MCP server a custom connector. You add it once under Customize, authorize it with your Lovie account, then switch it on in the conversations where you want it.

The only value you need

https://mcp.lovie.co/mcp

Before you start

FreeWorks, but you may hold only one custom connector at a time. Remove the other one first.
Pro / MaxAdd it yourself, no approval needed. This is the path below.
Team / EnterpriseOnly an Owner or Primary Owner can add a custom connector. Members then click Connect on it — see the admin section further down.

Add the connector

  1. Open Claude — claude.ai in a browser, or the desktop app. Both use the same settings.
  2. Click your profile icon in the bottom-left corner, then Settings.
  3. In the settings sidebar choose Customize, and find the Connectors section. If you are following a guide that says Settings → Connectors, that is the old location. Connectors moved under Customize; the page itself is unchanged.
  4. Click the + button, then Add custom connector.
  5. Fill the dialog in:
    NameLovie
    Remote MCP server URLhttps://mcp.lovie.co/mcp
    Advanced settingsLeave empty.
    Advanced settings asks for an OAuth Client ID and OAuth Client Secret. Lovie registers your client automatically over Dynamic Client Registration, so both stay blank. Filling them in with values from somewhere else is the most common way to break this step.
  6. Click Add. Claude contacts the server and shows the Lovie connector with the tools it discovered.
  7. Click Connect on the Lovie row. A Lovie sign-in opens in a new tab. Approve access; the tab closes itself and the row turns connected.

Turn it on in a chat

Adding a connector does not enable it everywhere

Claude keeps connectors off by default in each conversation, so a freshly added server looks like it did nothing. In the chat, click the + at the lower-left of the composer, choose Connectors, and toggle Lovie on for that conversation.

Check it worked

Team and Enterprise

  1. Owner: open Organization settings → Connectors.
  2. Click Add, hover Custom, and select Web.
  3. Paste https://mcp.lovie.co/mcp, leave the advanced OAuth fields empty, and click Add.
  4. Members: go to Customize → Connectors, find Lovie (labelled Custom), and click Connect to sign in with their own Lovie account.

Each member authorizes individually, so everyone sees only the companies they are a member of. There is no shared credential to rotate.

If something goes wrong

SymptomCause
No Add custom connector buttonYou are a Team or Enterprise member. An Owner has to add it at the organization level first.
“Connector limit reached”Free plans hold one custom connector. Remove the existing one under Customize → Connectors.
Added, but Claude never calls itThe connector is off in this conversation. Use the composer’s + → Connectors toggle.
Sign-in loopRemove the connector and add it again. Tokens are stored per connector, and a half-finished authorization leaves a stale one.
Tools appear but every call is refusedYou are signed in to a Lovie account with no company yet. Ask Claude to form one, or finish onboarding at lovie.co.

Somewhere else

$_ Claude Code One command, then /mcp to sign in. Terminal ChatGPT Developer mode, then the Plugins page. Chat app {} OpenAI API Responses API — one tool block. API Cursor One click, or ~/.cursor/mcp.json. Editor Ma Manus Settings → Connectors → Custom MCP. Agent VS VS Code MCP: Add Server, or .vscode/mcp.json. Editor Windsurf Cascade → MCP Servers. Editor Gemini CLI gemini mcp add, then /mcp auth. Terminal Zed Settings → AI → MCP Servers. Editor Go Goose goose configure → Remote Extension. Agent ·· Any MCP client The endpoint, and what each client calls it. Reference