Lovable

Get the Lovable dashboard URL where the user can add a connector. Connectors must always be added through the dashboard — the MCP cannot add them programmatically. Use this tool to return the deep link the user should open.

Create a new Lovable project. Pass workspace_id and initial_message. If workspace_id is omitted and exactly one eligible workspace exists, Lovable uses it. If multiple workspaces can create projects, this returns available_workspaces; choose one or ask the user, then call create_project again with that workspace_id. Returns projectId when creation starts; call render_project_widget with that projectId to show build progress. Projects use Lovable's backend default stack and are full-stack TypeScript apps with Tailwind + shadcn/ui. To start the project from a design system (components, tokens, styles), pass design_systems with an ID from list_design_systems.

Create a workspace skill by adding skills/{skill_name}/SKILL.md to the workspace repo. Only workspace admins and owners can create skills. The markdown must include valid frontmatter with matching name and a description, for example: ---\nname: my-skill\ndescription: What this skill helps with\n---\n\n

My Skill\n...

Delete a workspace skill from the workspace repo. Only workspace admins and owners can delete skills. This removes the skill directory and cannot be undone except by recreating the skill.

Deploy (publish) a project to production hosting on lovable.app. Returns the live URL that anyone can visit.

Provision a cloud PostgreSQL database (Supabase) for a project. This operation takes 30-60 seconds. Only needed once — after enabling, the database persists. Returns the database status once provisioning completes.

Check whether a cloud database (PostgreSQL via Supabase) is enabled for a project. Call this first before querying or connecting — if not enabled, use enable_database to provision it.

Get the code diff from a message or commit. Pass message_id (from send_message) to see what the agent changed, or sha for a specific commit. Returns a unified diff.

Get a presigned URL to upload a file. Workflow: 1) call this to get upload_url and file_id, 2) PUT the file content to the upload_url, 3) pass the file_id in the files array of send_message or create_project.

Get the authenticated user's profile and workspaces

Get the status and content of a message. Pass the message_id and thread_id returned by send_message for thread-aware status. Check the response status field: 'in_progress' means the agent is still working, 'completed' means done.

Get details for a specific project. Returns editor_url (Lovable editor) and preview_url (static preview, always available after first prompt). Includes a screenshot of the app when the project status is completed.

Get historical analytics for a published project: visitors, pageviews, bounce rate, session duration, and breakdowns by page, source, device, and country.

Get real-time visitor trend for a published project. Returns the current visitor count and visit counts in 5-minute intervals over the last 30 minutes.

Get a project's knowledge content. Knowledge is custom instructions that guide the AI agent's behavior for this specific project.

Get details for a specific workspace: plan, credit balance, member count, and settings. Use to check available credits before starting work.

Get the workspace's knowledge content. Knowledge is custom instructions that guide the AI agent's behavior across all projects in the workspace.

Get a workspace skill, including its full SKILL.md contents. Use this before update_workspace_skill when preserving existing content.

Deprecated: use create_project instead. This tool exists only for legacy published clients that hard-code it, and it is a strictly narrower alias — it cannot target a workspace, attach files, start from a template or design system, or wait for the build. Start building a new Lovable project from a prompt. If exactly one workspace can create projects, the project is created immediately and projectId is returned. If multiple workspaces are available, this returns workspaces for selection; choose one or ask the user, then call create_project with that workspace_id and the same prompt as initial_message.

List all connectors (integrations) available in a workspace. Connectors give the AI agent access to external services like Stripe, Supabase, Shopify, Slack, and more. Grouped by type: standard (OAuth-based API connectors), seamless (zero-config integrations), and MCP (Model Context Protocol servers). Each includes its enabled/disabled status. See https://docs.lovable.dev/integrations/introduction for details.

List connectors that have been added to a workspace (both from the catalog and custom). These are the connectors the AI agent can use during chat. To add a new one, call add_connector to get the dashboard URL the user should open.

List design systems available in a workspace. A design system is a reusable Lovable project that ships components, tokens, and styles. Pass any of these IDs as design_systems to create_project to start a new project from that design system.

List the edit history of a Lovable project. Each edit represents a code change with a commit_sha that can be used with get_diff. Supports cursor pagination via the cursor parameter (use pagination.next_cursor from the previous page).

List a page of files in a Lovable project. Optionally pass latest_commit_sha from get_project, or commit_sha from send_message/list_edits. Use pagination.next_cursor to fetch more pages.

List recent messages in a project, newest first. Use this to discover message IDs when you only have a project_id — for example, to fetch the latest assistant response with get_message or look up a diff with get_diff. Paginate older history by passing pagination.next_cursor as cursor.

Search and list projects in a workspace. Supports full-text search by name, AI-generated description, creator name, or email. Uses ngram matching for fuzzy search. Supports filtering by visibility, publish status, folder, and creator.

List available template projects in a workspace. These can be used as template_project_id when creating a project to clone the template's codebase.

List workspace skills. Skills are reusable agent instructions stored in the workspace repo and available to projects in that workspace. Use this before updating or deleting a skill.

List all workspaces the user belongs to. Returns a concise summary; use get_workspace for full details. Call this first to discover workspace IDs, which are required by project creation, workspace settings, and connector management tools.

Move one or more projects into a workspace folder. Existing folder memberships are removed first. The folder may update project visibility to match folder visibility; the response lists added, skipped, and visibility-updated projects.

Get a link for the user to edit their website in Lovable.

Use when user wants to modify, edit, or add features to an existing website.

Websites can only be edited in Lovable's web interface, not here.

Execute a SQL query against a project's cloud PostgreSQL database. Returns rows as JSON objects. Supports SELECT, INSERT, UPDATE, DELETE, and DDL statements. The database must be enabled first (use get_database_status to check, then enable_database if needed). Caution: write operations (INSERT, UPDATE, DELETE, DROP) modify production data permanently — prefer SELECT for inspection unless a write is explicitly required.

Read the contents of a single file in a Lovable project. Optionally pass latest_commit_sha from get_project, or commit_sha from send_message/list_edits. Returns the raw file content as text.

Remix (fork) an existing project into a workspace. Creates a copy of the source project. Waits for the remix to complete and returns the new project details.

Render the Lovable project status widget for a project that already exists. Call only after create_project returns projectId. Returns widget bootstrap data and does not create or modify projects.

Send a chat message to a project's AI agent and wait for the agent to finish. The agent can write and edit code, install npm packages, create pages and components, set up authentication, connect integrations (Stripe, Supabase, etc.), and fix bugs. Write messages in natural language — describe what you want, not how to implement it. Attach images (designs, screenshots) to guide visual changes. Returns the agent's response, activity log, and any edits made. The preview_url is rebuilt once the agent finishes. Set wait=false to return immediately without waiting.

Set a folder's visibility. 'personal' restricts to the creator and collaborators. 'workspace' makes it visible to all workspace members. Changing visibility propagates to all projects in the folder. Nested folders cannot change visibility (move to root first). Personal folders require a Business or Enterprise plan.

Set a project's knowledge content. Knowledge is custom instructions that guide the AI agent's behavior for this specific project. Max 10,000 characters. Caution: this replaces existing knowledge entirely — read with get_project_knowledge first if preserving existing content. Examples of useful knowledge: coding conventions, preferred libraries, brand voice guidelines, API endpoint patterns, or 'always use Supabase for auth'.

Set a project's visibility. 'private' makes it editable by workspace members. 'workspace_view' makes it visible (read-only) to workspace members (requires Business plan or higher). 'public' makes it visible to anyone (not available on enterprise plans). 'draft' makes it visible only to the creator (requires Business plan or higher).

Set the workspace's knowledge content. Knowledge is custom instructions that guide the AI agent's behavior across all projects in the workspace. Max 10,000 characters. Caution: this replaces existing knowledge entirely — read with get_workspace_knowledge first if preserving existing content. Examples of useful knowledge: coding conventions, preferred libraries, brand voice guidelines, API endpoint patterns, or 'always use Supabase for auth'.

Update a workspace skill by replacing skills/{skill_name}/SKILL.md in the workspace repo. Only workspace admins and owners can update skills. Read the existing skill first with get_workspace_skill if you need to preserve content.