Client Setup

Connect your favorite MCP client to the Lovelace platform

The Lovelace MCP server works with any client that supports the Model Context Protocol. This page covers setup for the most popular clients.

Claude Desktop

Open your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/claude/claude_desktop_config.json

Remote Server

{
  "mcpServers": {
    "lovelace": {
      "type": "streamable-http",
      "url": "https://mcp.uselovelace.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Local Server

{
  "mcpServers": {
    "lovelace-local": {
      "command": "lovelace",
      "args": ["mcp", "serve"],
      "transport": "stdio"
    }
  }
}

After saving, restart Claude Desktop. The Lovelace tools will appear in the tools menu.

Claude Code

Remote Server

claude mcp add lovelace --transport streamable-http \
  --url https://mcp.uselovelace.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Local Server

claude mcp add lovelace-local -- lovelace mcp serve

Verify the connection:

claude mcp list

Cursor

Open Cursor Settings and navigate to the MCP section, or edit ~/.cursor/mcp.json:

Remote Server

{
  "mcpServers": {
    "lovelace": {
      "type": "streamable-http",
      "url": "https://mcp.uselovelace.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Local Server

{
  "mcpServers": {
    "lovelace-local": {
      "command": "lovelace",
      "args": ["mcp", "serve"],
      "transport": "stdio"
    }
  }
}

Windsurf

Open Windsurf settings and navigate to the MCP configuration section, or edit ~/.windsurf/mcp.json:

Remote Server

{
  "mcpServers": {
    "lovelace": {
      "type": "streamable-http",
      "url": "https://mcp.uselovelace.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Local Server

{
  "mcpServers": {
    "lovelace-local": {
      "command": "lovelace",
      "args": ["mcp", "serve"],
      "transport": "stdio"
    }
  }
}

Generic / Custom Clients

Any client implementing the MCP specification can connect to the Lovelace server.

Streamable HTTP (Recommended)

Connect to the remote server via Streamable HTTP transport:

• Endpoint: https://mcp.uselovelace.com/mcp
• Method: POST for messages, GET for SSE stream
• Authentication: Authorization: Bearer YOUR_API_KEY header
• Content-Type: application/json

SSE (Legacy)

For clients that only support Server-Sent Events:

• SSE Endpoint: GET https://mcp.uselovelace.com/mcp
• Messages Endpoint: POST https://mcp.uselovelace.com/mcp/messages?sessionId=SESSION_ID

stdio (Local)

For local connections via the Lovelace CLI:

lovelace mcp serve

This starts an MCP server over stdio, using your existing Lovelace CLI session for authentication.

Connecting Both Remote and Local

You can connect to both the remote server and local server simultaneously. This gives you:

• Remote tools for platform operations (agents, knowledge, workspaces)
• Local tools for system-level operations (daemon management, local auth)

{
  "mcpServers": {
    "lovelace": {
      "type": "streamable-http",
      "url": "https://mcp.uselovelace.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    },
    "lovelace-local": {
      "command": "lovelace",
      "args": ["mcp", "serve"],
      "transport": "stdio"
    }
  }
}

Troubleshooting

Connection refused or timeout:

• Verify your API key is valid on the API Keys page
• Check that your network allows HTTPS connections to mcp.uselovelace.com

Tools not appearing:

• Restart your MCP client after changing configuration
• Verify the configuration file syntax is valid JSON

Authentication errors:

• Ensure the Authorization header includes the Bearer prefix
• Check that your API key has the required scopes (read, write)

Local server not starting:

• Ensure the Lovelace CLI is installed: lovelace --version
• Ensure you are logged in: lovelace auth status