Skip to main content
Wire Lovable’s in-editor agent to the hosted ish MCP server so it can call ish tools (study_create, study_add_iteration, study_run, and the rest) while you build. The server lives at https://mcp.ishlabs.io/mcp, speaks streamable HTTP, and signs you in over OAuth on first connect, so no token lands in a config file. For the full add mechanism and the OAuth handshake, see connect an agent. The one thing that differs for Lovable: ish runs simulated people from the cloud, so the study URL must load without your Lovable session. The in-editor preview is gated to you, so a URL that works in your tab fails silently for ish. Most of this page is about getting that URL right.

​
Connect

Add the ish server inside Lovable’s MCP settings, pointing at the hosted endpoint: 
https://mcp.ishlabs.io/mcp
The agent signs in over OAuth on first connect. ish reads the clientInfo Lovable sends in the MCP handshake, recognizes the lovable client, and tailors the URL guidance below to Lovable’s share and publish paths.
Use https://mcp.ishlabs.io/mcp with no trailing slash. The /mcp/ form triggers a redirect (HTTP 307) that some clients will not follow on a POST, leaving the agent with an empty tool list.

​
Confirm the connection

Ask the agent a read-only question. A read confirms the connection without drawing any credits: 
Use the ish tools to confirm who I am and list my workspaces.
The agent calls workspace_get and reports your workspaces back. A brand-new account shows an empty list, which is still a successful connection.
The agent returns a workspace list (or an explicit empty list) instead of “no ish tools available”. That means the OAuth sign-in landed and the tools are live.

​
Point a study at a reachable URL

When you create an interactive iteration against a Lovable URL, ish has to load that URL from a cloud browser that does not carry your Lovable session. The trap: a Lovable preview URL is a public hostname, so it passes ish’s localhost check, yet still shows a login wall to anyone but you. Pick the link type that loads without your session.
Lovable URLReachable for ish?Use it
In-editor preview (id-preview--…, no token)No, gated to your sessionShare or publish first
Share preview link (carries the access token)Yes, until the token expires (~7 days)Good for a quick run
Published site (<slug>.lovable.app)Yes, permanently publicBest for a study you reuse
1

Get a public link in Lovable

Open Share and pick Share preview for a public preview link, or Publish and use the published <slug>.lovable.app URL. The published URL is permanent; the share-preview link carries a signed access token that expires in about seven days.
2

Create the iteration against that URL

Tell the agent to add an interactive iteration pointed at the link. Under the hood it calls study_add_iteration with platform="browser" and the public url. You set this once per study; later runs reuse the same iteration.
Create an interactive study for my workspace and add an iteration pointed at
https://my-app.lovable.app, then run it for five people.
3

Read the reactions

After study_run completes, ask the agent for the summary. study_get with view="summary" returns the journey: what people noticed, where they got stuck, and the reasoning behind each reaction. You get a narrative, not a single score.

​
What ish tells the agent

ish steers the agent for you. When the iteration’s URL is a Lovable host, the study_add_iteration response carries a notes hint resolved from the link itself:
ish returns the gated-URL hint: the in-editor preview is login-gated and will fail silently, so open Share → Share preview for a public preview link (stays live about seven days), or Publish and use the published URL.
A published <slug>.lovable.app URL is permanently public, so ish returns no reachability warning. The study just runs.

​
When the page needs a login you cannot remove

If the part of the app under test sits behind a real sign-in that you cannot publish around, register the access once on the workspace instead of fighting the gate. Then every interactive study you point at that origin reuses it. 
Register a session cookie for my staging origin so ish can load the gated page, then
run the study.
ish can sign in three ways: HTTP basic auth, a session cookie, or a login form the participant fills in. See site access for which method matches your gate and how an origin gets bound.

​
Share the results

Lovable’s agent can create and run studies, but it cannot mint a public results link. Sharing is a CLI action: ish study share returns a public, no-login share_url to paste into an email or hand to a stakeholder. See sharing results for the lifecycle and what a viewer sees.
A share link points at one study’s results. The Lovable URL above points at the app the simulation experiences. Two different links for two different jobs.

​
Troubleshooting

The OAuth step did not complete. Reconnect the ish server in Lovable’s MCP settings, approve the sign-in in your browser, then ask again. Confirm the URL has no trailing slash.
The study is pointed at a gated URL. The in-editor preview loads only with your session. Switch the iteration to a Share preview link or a published <slug>.lovable.app URL, or register a login with site_access_set.
A Lovable share-preview token expires in about seven days. Regenerate the link in Share → Share preview and update the iteration’s URL, or publish the site for a permanent URL that never expires.

​
Next steps

Run a study

Every parameter for study_create, study_add_iteration, and study_run.

Site access

Reach a gated URL with basic auth, a cookie, or a login form.

Sharing results

Mint a public, no-login link to a study’s results from the CLI.

Other clients

Wire Replit, Bolt, v0, Claude Code, and more.