Skip to main content

Client Setup

Connect your MCP client to the Lovelace public gateway

All public client configurations should point to the same gateway:

  • Endpoint: https://mcp.uselovelace.com/mcp
  • Transport: Streamable HTTP
  • Auth discovery: MCP 401 challenge plus Protected Resource Metadata

For the public remote gateway, prefer clients that can follow the MCP authorization flow automatically. See Authentication.

Claude Desktop

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\\Claude\\claude_desktop_config.json
  • Linux: ~/.config/claude/claude_desktop_config.json
json
{
  "mcpServers": {
    "lovelace": {
      "type": "streamable-http",
      "url": "https://mcp.uselovelace.com/mcp"
    }
  }
}

Restart Claude Desktop after saving.

Claude Code

bash
claude mcp add lovelace --transport streamable-http \
  --url https://mcp.uselovelace.com/mcp

Verify with:

bash
claude mcp list

Cursor

Edit ~/.cursor/mcp.json or use the MCP settings UI:

json
{
  "mcpServers": {
    "lovelace": {
      "type": "streamable-http",
      "url": "https://mcp.uselovelace.com/mcp"
    }
  }
}

Windsurf

Edit ~/.windsurf/mcp.json or use Windsurf's MCP settings UI:

json
{
  "mcpServers": {
    "lovelace": {
      "type": "streamable-http",
      "url": "https://mcp.uselovelace.com/mcp"
    }
  }
}

Generic / Custom Clients

Use the same public contract:

  • URL: https://mcp.uselovelace.com/mcp
  • MCP transport: Streamable HTTP
  • Authorization: support MCP auth discovery against the gateway’s 401 challenge

The public gateway exposes:

  • Protected Resource Metadata: https://mcp.uselovelace.com/.well-known/oauth-protected-resource
  • Protected resource: https://mcp.uselovelace.com/mcp

The public gateway accepts MCP messages at POST /mcp. Sessions are tracked with the mcp-session-id header and may be terminated with DELETE /mcp. Most MCP clients manage session headers automatically.

Local Server

For local Lovelace workflows, use the local MCP server instead:

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

See Local Server for details.

Troubleshooting

Connection errors

  • Confirm the endpoint is https://mcp.uselovelace.com/mcp
  • Confirm your client supports Streamable HTTP MCP servers
  • Restart the client after changing configuration

Authentication errors

  • Confirm the client supports MCP authorization discovery for remote HTTP servers
  • Confirm the client is using the Lovelace MCP endpoint as the protected resource/audience
  • Confirm the granted token has the required scopes

Tools missing

  • Verify the connection with “List my Lovelace workspaces”
  • Recheck JSON syntax in your client configuration