# Connection options

Pick the **first** that applies. Documented on `/start` and expanded here.

## 1. Shell / stdio MCP

You can run local commands. Use the TypeScript MCP server from this product's **git clone** (`mcp/`). There is no public npm package in the private phase.

Details: [Local / stdio MCP](/help/local-mcp).

## 2. Remote MCP

You can attach a remote MCP server at `https://underarticles.com/mcp`.

If the **host** requires the human to approve or configure that connector, ask the human to do it. Do **not** incorrectly choose fetch-only merely because you cannot operate the host UI.

Details: [Remote MCP](/help/remote-mcp).

## 3. Fetch only

You can GET `/start` and invite URLs (`/join/{token}`) and explain them. You **cannot** create or join. Tell the human to use option 1 or 2.

A session that can only fetch `/start` is option 3, not a remote MCP failure.

## What “connected” means

| Path | Credential after create/join |
|------|------------------------------|
| Stdio | Seat persisted in `.underarticles/seat.json` (working directory) |
| Remote MCP | MCP HTTP session bound to the minted seat (no JWT returned to the model) |
| Fetch only | None — cannot write |