Lovelace MCP Server
The entire Lovelace platform as a single MCP server
Connect any MCP-compatible client — Claude Desktop, Claude Code, Cursor, Windsurf, or your own — to the full Lovelace platform through a single endpoint. Spawn agents, manage workspaces, search knowledge, and more, all through the Model Context Protocol.
How It Works
The Lovelace MCP server exposes the platform's core capabilities as MCP tools and MCP resources over a standard Streamable HTTP transport:
- Tools let you take actions: spawn agents, create workspaces, store knowledge
- Resources let you read data: workspace details, agent status, knowledge documents
You can connect remotely via mcp.uselovelace.com or locally via the Lovelace daemon.
What You Can Do
| Capability | Tools | Description |
|---|---|---|
| Workspaces | lovelace_list_workspaces, lovelace_get_workspace | Browse and inspect your workspaces |
| Agents | lovelace_spawn_agent, lovelace_list_agents, lovelace_get_agent_status, lovelace_get_agent_result | Spawn agents, monitor execution, retrieve results |
| Knowledge | lovelace_search_knowledge, lovelace_store_knowledge | Search and store documents in the knowledge base |
Quick Start
Remote (recommended):
Add this to your MCP client configuration:
json
{
"mcpServers": {
"lovelace": {
"type": "streamable-http",
"url": "https://mcp.uselovelace.com/mcp"
}
}
}
Local:
json
{
"mcpServers": {
"lovelace-local": {
"command": "lovelace",
"args": ["mcp", "serve"],
"transport": "stdio"
}
}
}
See the Quick Start guide for a complete walkthrough, or jump to Client Setup for your specific editor.
Documentation
- Quick Start — Connect and make your first tool call in 5 minutes
- Authentication — OAuth 2.1 flow, API keys, and token management
- Tools Reference — Complete reference for all available tools
- Resources Reference — Resource URI scheme and available resources
- Client Setup — Configuration for Claude Desktop, Claude Code, Cursor, Windsurf, and more
- Local Server — Run the MCP server locally via the Lovelace daemon