MCP server

What it is

MCP (Model Context Protocol) is the open standard Claude and other agents use to call external tools. kinapi-mcp-server exposes the whole v1 API as a set of tools: create and read check-ins, check the report at SES, download the signed contract, manage properties. The agent already knows when and how to use them — you do not explain endpoints to it or write it a client.

Compared with integrating the REST API directly

It does not replace the API — it is another way of talking to it. What changes is what you have to build:

• No HTTP client. You install the package and that is it: no managing auth headers, serialising JSON or mapping responses by hand.
• Errors the agent understands, not JSON to parse. A 404 does not arrive as a bare {"error":"not found"}: it arrives as “that check-in does not exist, check the reservationId”, so the agent can react or ask you instead of falling over.
• It chains calls without you programming the orchestration. “Cancel booking R-2026-0412 and confirm it went through” is two API calls resolved by the agent from one request of yours.
• Anyone on the team can use it, not just whoever writes code. Support or operations can ask Claude for a guest’s status without touching code or opening the panel.
• One line to install. npx downloads and runs it; there is nothing to clone and no TypeScript to compile.

Installation

In Claude Desktop, Claude Code or any MCP client, add this to its configuration (`claude_desktop_config.json` or `.mcp.json`):

{
  "mcpServers": {
    "kinapi": {
      "command": "npx",
      "args": ["-y", "kinapi-mcp-server"],
      "env": {
        "KINAPI_API_KEY": "kinapi_…"
      }
    }
  }
}

The API key is the same one you generate in the panel (Settings → API) — see Authentication.

Available tools

Package

Published on npm as kinapi-mcp-server. Version 0.8.0 adds records exports, the proof of filing and the owner filter on kinapi_list_checkins (see Exports and offboarding).