Live MCP endpoint — no API key, no local proxy
Lovie

Model Context Protocol

Lovie, inside your AI client.

Add the endpoint below to Claude, ChatGPT, Cursor, Manus or any MCP-aware client, and your agent can work your banking, cap table, accounting and company formation directly from the conversation.

https://mcp.lovie.co/mcp

Pick your client

Every client asks for the same URL under a different menu. Pick yours for the exact clicks, keystrokes and config keys — each page was checked against that vendor’s own documentation on 30 August 2026.

Claude Web, desktop, mobile and Cowork. Chat app $_ 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

No client at all

Not every conversation happens in an MCP client. The same agent, over the same tools, answers on the channels below — nothing to install, no config file, no endpoint to paste.

Phone +1 628 257 8355 WhatsApp +1 856 491 0472 iMessage +1 628 257 8355 Telegram @lovieco_bot Email [email protected]

The difference is who hosts the conversation. Above, your client hosts it and Lovie is the server it connects to. Here, Lovie hosts it and you just write.

Landed here from a browser?

That is expected — an MCP endpoint speaks a protocol, not HTML, so there is nothing to click. Paste the URL above into your client’s MCP settings instead. The endpoint is working; this page is just the human-readable side of it.

In a hurry

Claude Code

one command

claude mcp add --transport http lovie https://mcp.lovie.co/mcp

Then run /mcp in a session and authenticate. Scopes and the rest ›

Signing in

There are no API keys. Discovery is anonymous: your client can connect, list tools and read the open ones without any credentials. The first time it calls a tool that touches your company, the server answers with an OAuth challenge, your client opens a Lovie sign-in, and it stores the resulting token itself.

Some hosts only authorize at the moment you add a connector, and treat an anonymous handshake as proof that the server needs no sign-in. Those clients should use https://mcp.lovie.co/mcp-eager, which forces the OAuth challenge during the handshake. The protocol details ›

Identity is issued by https://clerk.lovie.co.

Try saying

What your agent can do

340 tools across 18 domains, discovered live from the running services. 38 work anonymously; the rest ask you to sign in the first time they run.

▸ account 3
▸ accounting 35
▸ billing 13
▸ card 10
▸ company 164
▸ counterparty 3
▸ document 13
▸ field 9
▸ identity 3
▸ insight 4
▸ integration 9
▸ itin 13
▸ kyc 2
▸ notification 2
▸ payments 9
▸ signature 10
▸ trademark 25
▸ transaction 13