# Quickstart

> Add the Kinro MCP server to Claude, ChatGPT, Codex, Cursor, VS Code or any MCP client. No account or API key.

Kinro's MCP server is hosted. There is nothing to install and nothing to sign up for: add the URL to your client and start a conversation.

| Setting        | Value                                     |
| -------------- | ----------------------------------------- |
| URL            | `https://api.kinro.com/mcp`               |
| Transport      | Streamable HTTP (`POST`, JSON responses)  |
| Authentication | None                                      |
| Tool timeout   | At least 60 seconds; 320 seconds in Codex |

> **Important:** Every conversation on `https://api.kinro.com/mcp` is a real insurance request, handled by a licensed brokerage. Use it for real businesses and real questions. To build or test an integration, use the [test endpoint](#test-your-integration).

## Claude

**Claude Code:**

```bash
claude mcp add --transport http kinro https://api.kinro.com/mcp
```

**Claude apps:** open Settings, then Connectors, choose **Add custom connector**, and enter `https://api.kinro.com/mcp` with no authentication.

## ChatGPT

Custom apps require a ChatGPT plan and workspace permissions that support developer mode. Follow [OpenAI's current setup instructions](https://help.openai.com/en/articles/12584461-developer-mode-and-mcp-apps-in-chatgpt) if the controls below are unavailable.

1. In ChatGPT on the web, open **Settings**, then **Apps**, then **Advanced settings**, and enable developer mode. Your workspace administrator may need to grant access first.
2. Create an app with the URL `https://api.kinro.com/mcp` and authentication set to **none**, scan its tools, and finish creating it.
3. Start a new chat, select the Kinro app, and ask about business insurance.

In ChatGPT, users can also attach insurance documents. Other agents send documents as base64; see [Documents](/docs/documents).

## Codex

```bash
codex mcp add kinro --url https://api.kinro.com/mcp
```

Then raise the tool timeout in `~/.codex/config.toml`, because Kinro's replies can take longer than a minute and update checks wait for news:

```toml
[mcp_servers.kinro]
url = "https://api.kinro.com/mcp"
tool_timeout_sec = 320
```

## Cursor

Add Kinro to `~/.cursor/mcp.json` (or `.cursor/mcp.json` in a project):

```json
{
  "mcpServers": {
    "kinro": { "url": "https://api.kinro.com/mcp" }
  }
}
```

## VS Code

Add Kinro to `.vscode/mcp.json`:

```json
{
  "servers": {
    "kinro": { "type": "http", "url": "https://api.kinro.com/mcp" }
  }
}
```

## Any other MCP client

Configure a remote MCP server using Streamable HTTP at `https://api.kinro.com/mcp` with no authentication. The server is stateless: it issues no `Mcp-Session-Id`, and each HTTP request carries one JSON-RPC message. Send `Accept: application/json, text/event-stream` on every request.

To list the tools from a terminal:

```bash
curl -sS https://api.kinro.com/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

Calling `ask_kinro` the same way opens a real insurance request:

```json
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "ask_kinro",
    "arguments": {
      "message": "I run a two-person painting company in Austin. What insurance do I need, and what would it cost?"
    }
  }
}
```

The result carries Leo's reply and a `conversation_id`. Pass that ID on every later call in the same conversation. [Conversations](/docs/conversations) explains the full loop.

## Test your integration

Use Kinro's test endpoint while you build, and switch to production when you are ready:

```text
https://api-preview.kinro.com/mcp
```

It has the same tools and behaves the same way, with these differences:

- **Test quotes, not coverage.** Conversations create test-side request records. Available quotes use carriers' test systems, so they do not represent an offer of real insurance or start coverage. Some coverage may be unavailable for testing.
- **Use made-up business details.** Do not share real customer information. This endpoint is not isolated from all outside communication: contact details you supply may receive real messages. Omit contact details or use only addresses and numbers you control.
- **It changes first.** The test endpoint runs Kinro's newest version before production. It can behave differently from production for a short time, or be briefly unavailable.

Give the two connections different names in your client, such as `kinro` and `kinro-test`, so a test conversation never goes to production.

## Your first conversation

1. Ask your assistant a business insurance question and let it call `ask_kinro` with your words.
2. Answer Leo's follow-up questions about the business. Your assistant relays them.
3. When Leo says it is pricing a quote, your assistant checks back with `ask_kinro` without a message until the quote arrives, usually within a few minutes.
4. Review the quote. The message lists the available price, limits, dates and exclusions, with a link to the full quote on kinro.com.

---

Source: https://kinro.com/docs/quickstart. All Kinro docs: https://kinro.com/docs/llms.txt