Skip to main content
This walks one agent through one happy path: connect a client to the hosted ish MCP server, confirm ish is reachable, and read back a reaction. It takes under five minutes. The hosted server lives at https://mcp.ishlabs.io/mcp. It speaks streamable HTTP and handles sign-in over OAuth the first time a client connects, so you never paste a token into a config file. By the end, your agent can call ish as a set of tools and report back what a simulated person noticed.
You need an ish account. If you do not have one, get ish free first. The OAuth step below signs the client in as you.

​
Step 1: connect a client

Pick the client you already work in. Each one connects to the same URL.
Add the server at user scope:
claude mcp add --transport http --scope user ish https://mcp.ishlabs.io/mcp
Claude Code discovers ish’s OAuth metadata, registers itself, opens your browser to sign in, and stores the resulting token. Cursor and Claude Desktop connect the same way against the same URL.
Always use https://mcp.ishlabs.io/mcp with no trailing slash. The /mcp/ form triggers a redirect that some clients will not follow on a POST, leaving the agent with an empty tool list.

​
Step 2: confirm ish is connected

Reconnect or restart the client so it runs the OAuth flow, then ask the agent a read-only question. A read confirms the connection without drawing any credits. In the agent, ask: 
Use the ish tools to confirm who I am and list my workspaces.
The agent calls workspace_get (a read-only tool) and reports your workspaces back. If ish is connected, you see at least one workspace; a brand-new account shows an empty list, which is still a successful connection. Clients that read MCP resources also surface ish://identity/me, the decoded identity for the session.
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.
If the agent reports no ish tools, the OAuth step did not complete. Reconnect the client and approve the sign-in in your browser, then ask again.

​
Step 3: read your first reaction

Now run something and read back what a simulated person made of it. The fastest path is to run a study that already exists in your workspace. Tell the agent: 
Find a study in my workspace, run it for a few people, and tell me what they noticed.
Under the hood the agent works through ish’s tools:
1

Discover a study

The agent calls study_get with your workspace_id to list studies and pick one.
2

Run it

It calls study_run with a small audience and wait=True, which blocks until every simulated person reaches a terminal state.
3

Read the reactions

It calls study_get with view="summary" and reports back the journey: what people noticed, where they got stuck, and the reasoning behind each reaction.
You get a narrative reaction with the reasoning attached, not a single score. That is the loop: simulate a visit, read what landed, decide what to change.
No study in this workspace yet? Ask the agent to create one first (“create a study that points simulated readers at this URL and asks what they noticed”), then run it. The study_create and study_run tools cover both.

​
Where to go next

Every MCP tool

All 42 hosted tools, grouped by domain, each with its annotation tier.

MCP resources

The ish:// resources for identity, docs, screenshots, and media.

Run a study

Create, iterate, run, and read studies across every modality.

The ish CLI

Drive the same platform from your terminal and from CI.