ChatGPT

ChatGPT reaches custom MCP servers through Developer mode. Both the toggle and the page that holds connectors were renamed in July 2026, so most guides on the web send you to menus that no longer exist.

The only value you need

https://mcp.lovie.co/mcp

Time 3 minutes
Transport HTTP streamable
Auth OAuth — in-chat
Needs Developer mode

The menus moved in July 2026

Developer mode used to live under Connectors → Advanced, and the page that holds connectors was called Connectors. The toggle is now under Security and login, and the page is called Plugins. Guides that send you to Connectors → Advanced settings are describing a menu that no longer exists — that is why the section looks missing.

Before you start

Developer mode is available on Plus and Pro, and on Business, Enterprise and Edu where the workspace allows it.
A workspace admin can switch Developer mode off for everyone, or allow only specific connectors. If the toggle is missing entirely, that is why.
ChatGPT connects only to remote MCP servers over HTTPS. There is no local stdio option, which is fine here — Lovie is remote, with nothing to install.

Enable Developer mode

Click your profile picture, then Settings.
Select Security and login.
Turn on Developer mode.

Add Lovie

Go to Plugins — from Settings, or the Plugin Directory. The + button appears here only once Developer mode is on.
Click the + button.
Fill in the two user-facing fields:

Name Lovie

Description Banking, cap table, accounting and US company formation
Under Connection, choose Public endpoint and paste the URL including the /mcp path:
https://mcp.lovie.co/mcp
Pasting the bare hostname is the most common failure here. Without /mcp you get the page you are reading, not the protocol endpoint.
Create the connection. ChatGPT handshakes with the server and shows the tools and metadata it discovered.
Open a new chat and enable Lovie from the tools menu for that conversation.

Signing in

Lovie does not demand credentials to be added. Discovery is anonymous, so the connector appears connected straight away with its tool list. The first time you ask for something that touches your company, Lovie answers with a sign-in link inside the conversation rather than failing the call — click it, approve, and ask again.

That in-chat link exists because ChatGPT does not surface a plain HTTP authorization challenge to you. Lovie detects an OpenAI client and returns the challenge as part of the tool result instead, which is what makes it clickable.

Check it worked

“Ask Lovie which of my invoices are overdue.”
“Summarize my spending this month by category.”

If something goes wrong

Symptom	Cause
No Developer mode toggle	Wrong menu, or a workspace policy. It is under Settings → Security and login, not under Plugins.
No + on the Plugins page	Developer mode is still off. The button is what it unlocks.
“Could not reach the server”	The URL is missing `/mcp`.
Tools listed, calls do nothing	The connector is not enabled in this conversation. Turn it on in the tools menu.
Sign-in link never appears	The tool you asked for is one of the open ones and needs no account. Ask for something company-scoped, such as your cap table.

Somewhere else

Claude Web, desktop, mobile and Cowork. Chat app $_ Claude Code One command, then /mcp to sign in. Terminal {} 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

Name	`Lovie`
Description	`Banking, cap table, accounting and US company formation`