Lovie MCP›Manus

Agent

Manus

Manus authorizes a connector at the moment you add it, not on the first tool call. Lovie recognizes it by name and raises the sign-in during the handshake, so the plain endpoint is the right one — there is nothing extra to configure.

The only value you need

• Time 2 minutes
• Transport HTTP streamable
• Auth OAuth — at add time
• Endpoint plain /mcp

Add the connector

1. Open Settings from the Manus sidebar.
2. Select Connectors.
3. Click + Add connectors.
4. In the dialog, switch to the Custom MCP tab.
5. Click + Add custom MCP, then choose Direct configuration.
6. Fill it in:

   Name	Lovie
   Transport type	HTTP — leave it as it is
   Server URL	https://mcp.lovie.co/mcp

7. Click Save. Manus contacts the server and retrieves the tool list.
8. A browser window opens on the Lovie authorization page. Approve it. The connector goes green.
9. Enable Lovie in the task or session where you want the agent to use it.

Import by JSON instead

Same dialog, the Import by JSON option. Paste this:

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

Check it worked

• “Using the Lovie connector, list my companies.”
• “Find every uncategorized transaction from last month and categorize it.”

If something goes wrong

Symptom	Cause
“Could not connect” on Save	The URL is missing the /mcp path, or transport was switched to SSE. It must be HTTP.
Connected, but no authorization window	A popup blocker. Allow popups for Manus and re-add the connector.
Agent never uses the tools	The connector is added but not enabled for this task. Turn it on in the task’s tool list.
Every call is refused after signing in	You approved with a Lovie account that has no company. Ask Manus to form one, or finish onboarding first.

Somewhere else