Lovie MCP›Claude Code

Terminal

Claude Code

Claude Code adds remote servers from the shell and runs the OAuth flow from inside a session. Pick the scope deliberately — it decides whether your teammates get the server too.

The only value you need

• Time 1 minute
• Transport HTTP streamable
• Auth OAuth — /mcp
• Config ~/.claude.json · .mcp.json

Add the server

That registers it for the current project only. Add --scope user to have it in every project you open, or --scope project to commit it for your team.

Choose the scope deliberately

Scope	Reach	Stored in
local default	This project, only you	~/.claude.json
user	Every project, only you	~/.claude.json
project	Everyone who clones the repo	.mcp.json (commit it)

--scope project shares the server, never a credential: each teammate signs in with their own Lovie account the first time they use it.

Sign in

1. Run claude mcp list. The lovie row should be there with a health status.
2. Start Claude Code in the project, then run the /mcp slash command.
3. Select lovie, then Authenticate. Your browser opens the Lovie sign-in.
4. Approve. Come back to the terminal — /mcp now shows connected.

On Claude Code 2.1.186 and later you can do the same without entering a session: claude mcp login lovie. claude mcp logout lovie clears the token.

Or write the file yourself

.mcp.json at the repo root, which is what --scope project writes:

{
  "mcpServers": {
    "lovie": {
      "type": "http",
      "url": "https://mcp.lovie.co/mcp"
    }
  }
}

Check it worked

$ claude mcp get lovie
$ claude
> using lovie, list my companies

Managing it later

Command	Does
claude mcp list	Every configured server plus a live health check
claude mcp get lovie	Scope, URL and connection detail for one server
claude mcp login lovie	Run the OAuth flow from the shell
claude mcp logout lovie	Forget the stored token
claude mcp remove lovie	Remove the server from its scope

If something goes wrong

Symptom	Cause
Added, but not listed	You added it at local scope in a different directory. Re-add with --scope user.
failed to connect	An outbound proxy is intercepting HTTPS. The endpoint needs a plain TLS connection; no proxy or npx wrapper belongs in front of it.
Every tool asks you to sign in again	Two Claude Code versions sharing one config. Run claude mcp logout lovie, then claude mcp login lovie once.

Somewhere else