Skip to main content
ish runs as a hosted MCP server at https://mcp.ishlabs.io/mcp. Any client that speaks MCP over streamable HTTP can call ish tools (study_run, ask_run, person_generate, and the rest) once it points at that URL and signs in. The endpoint and sign-in are the same everywhere; pages differ only in where the client keeps its config and what ish can do for that client. Pick yours below for the exact steps. These pages cover the MCP path. Local coding agents (Claude Code, Cursor, VS Code) can also drive ish through the CLI instead — and testing a web, iOS, or Android app on your own machine needs the CLI either way, since the hosted server can’t reach your localhost. You don’t need both; see the CLI and the MCP server.

Claude Code

Best for terminal-driven runs, wired with one command.

Cursor

Best for editor agents under a 30-second tool-call cap.

Claude Desktop

Best for desktop chat that reads ish resources in full.

ChatGPT

Best for chat where you read findings through tools, not resources.

VS Code

Best for Copilot agent mode, with the loopback-port OAuth handled for you.

Lovable

Best for testing a build, once you point ish at a reachable URL.

Replit

Best for a repl, pointed at a webview or deployment URL.

Bolt

Best for the embedded agent, pointed at a published preview.

v0

Best for the in-editor agent, pointed at a deployed URL.

Windsurf

Best for any MCP-over-HTTP setup the CLI can wire for you.
No card for your client? Any MCP client that speaks streamable HTTP works. Point it at https://mcp.ishlabs.io/mcp, sign in on first connect, and follow Connecting. More clients get their own page over time.
Every client uses the same endpoint and the same sign-in. The connecting guide owns the add mechanism and the OAuth handshake; the per-client pages above are the short, client-specific version.

​
How clients group

All clients reach the same server the same way. They differ in how much ish can do for them when you set up or run a study. There are three groups.
The ish CLI writes the MCP config block for Cursor, VS Code, Claude Code, Claude Desktop, and Windsurf. Run ish mcp add to plan and apply the change, ish mcp list to see what is wired, and ish mcp remove to unwire it. The CLI edits local JSON config files only; it never embeds a token, since the server handles OAuth on first connect. See the ish mcp reference.
Lovable, Replit, Bolt, and v0 build apps whose preview URLs are gated to your editor session. ish runs simulated people from the cloud, so a preview URL that loads in your tab fails silently for them. When ish detects one of these clients (or a study URL on a known builder host), it returns a hint that names the share or deploy path for that builder. The per-client pages above carry the exact steps.
Any other MCP client connects to https://mcp.ishlabs.io/mcp and runs every tool. ish recognizes the client from its handshake to tailor guidance, but the CLI does not write its config and there is no builder hint. ChatGPT is in this group and has its own page because it reads ish tools but not ish resources.

​
Other MCP clients

No page for your client? It still works. Point any MCP client that speaks streamable HTTP at https://mcp.ishlabs.io/mcp and sign in on first connect. This covers clients like Cline and Roo Code: add the server with their own MCP settings, using the URL above.
Use https://mcp.ishlabs.io/mcp with no trailing slash. A trailing slash redirects (HTTP 307) and breaks some clients, ChatGPT among them.
For the generic steps that work in any client, see Connecting.

​
Next steps

Connecting

The add mechanism and OAuth, in full.

Tool index

Every ish MCP tool, grouped by domain.