Kamai

io.kamaiv1.0.0Updated Sep 30, 2026

AI takeoff for construction: turn PDF blueprints into structured, traceable quantities.

VerifiedStreamable HTTPWeb executableData & AnalyticsFiles & StorageProductivity & Workflow

Overview

AI-generated overview

Connects an assistant to Kamai construction-blueprint projects so it can view blueprints, takeoff quantities and elements, and manage projects and uploads.

What it does
Provides tools and interactive widgets for Kamai construction-blueprint work: viewing projects and blueprints, showing measured takeoff quantities as a sortable table, and listing per-element rows such as rooms, walls, doors, windows and objects with outlines. It can create or rename projects, list, inspect and cancel processing jobs, and handle blueprint PDF uploads, including importing a PDF attached to a chat message. It also opens the Kamai app in a panel.
When to use it
Use it when an assistant needs to work with construction takeoffs from PDF blueprints inside Kamai: reviewing projects, checking measured quantities and elements, tracking processing jobs, or uploading new blueprints. It is aimed at Kamai users rather than general document handling.
Requirements
A remote endpoint at or a local stdio run with Bun 1.3.3 and Node.js 22.12 or newer. Local mode needs a Kamai personal API key in KAMAI_API_KEY and the API base URL in MCP_API_BASE_URL. HTTP mode needs MCP_PUBLIC_URL, MCP_AUTH_ISSUER and optionally MCP_AUTH_JWKS_URI, MCP_ACCEPTED_AUDIENCES, PORT and KAMAI_APP_ORIGINS, plus access to Kamai's MCP API and authorization server.
Before you install
The personal API key in KAMAI_API_KEY is sent as the bearer for every API call and the tools run as that key's owner, so treat it as a secret. Tools can create or rename projects, cancel processing jobs, and upload blueprint PDFs, which changes data in the Kamai account. Blueprint content and project data go to Kamai's API and authorization server.

Installation

In SourceWeft

  1. Open Kamai in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.kamai.io/mcp"
    }
  }
}

README

kamai-mcp

Kamai's MCP server: tools and MCP Apps widgets for Kamai construction-blueprint projects, blueprints and takeoffs. It runs against Kamai's MCP API and validates access tokens issued by Kamai's OAuth authorization server. It holds no Kamai secrets.

Tools

ToolWhat it does
view_projectsInteractive panel of the user's projects and blueprints
view_blueprintA blueprint page with its take-off shapes drawn on top
view_takeoffMeasured take-off quantities as a sortable table
list_elementsPer-element rows (rooms, walls, doors, windows, objects) with outlines
create_project, update_projectCreate or rename a project
list_jobs, get_job, cancel_jobProcessing jobs of a project
view_uploadUpload panel for a blueprint PDF
ingest_blueprint_from_chatImport a PDF attached to a ChatGPT message
open_kamaiOpen the Kamai app in a panel

list_projects, get_project, get_blueprint, request_blueprint_upload and finalize_blueprint_upload are app-only: callable by the widgets, not advertised to the model.

Run locally with your API key

The quickest way to run this server against your own Kamai data is local mode: the host spawns the server, talks to it over stdio, and the credential is a personal API key from Kamai (API Keys in the Kamai app) instead of OAuth.

bun installbun run build:widgetsKAMAI_API_KEY=... MCP_API_BASE_URL=https://mcp-api.kamai.io bun run local

Claude Code:

claude mcp add --env KAMAI_API_KEY=... --env MCP_API_BASE_URL=https://mcp-api.kamai.io \  --transport stdio kamai -- bun /path/to/kamai-mcp/src/local.ts

Claude Desktop (claude_desktop_config.json):

{ "mcpServers": { "kamai": {    "command": "bun", "args": ["/path/to/kamai-mcp/src/local.ts"],    "env": { "KAMAI_API_KEY": "...", "MCP_API_BASE_URL": "https://mcp-api.kamai.io" } } } }

The key is used as the bearer for every API call; the tools run as the key's owner.

Run the HTTP server

bun installcp .env.example .envbun run dev

The values in .env.example are placeholders: set MCP_PUBLIC_URL and MCP_AUTH_ISSUER to your tunnel and to a reachable authorization server before starting, or every request will be refused with invalid_token.

VariableMeaning
PORTListen port, default 8006
MCP_PUBLIC_URLThe URL hosts call and ask a token for (the resource in discovery); a tunnel, not localhost
MCP_AUTH_ISSUERIssuer of the access tokens, matched byte for byte against the token's iss
MCP_AUTH_JWKS_URIOptional. Defaults to {MCP_AUTH_ISSUER}/jwks.json
MCP_API_BASE_URLKamai MCP API base URL, https://mcp-api.kamai.io. Also the audience an access token must carry
MCP_ACCEPTED_AUDIENCESOptional comma-separated audiences, for a cutover. Defaults to MCP_API_BASE_URL
KAMAI_API_KEYLocal mode only: the personal API key the tools run as
KAMAI_APP_ORIGINSOptional comma-separated extra origins open_kamai may frame; the first becomes the default

The MCP API and the authorization server are operated by Kamai, so running the HTTP server end to end needs access to both. An MCP server is only really testable against a real host, and a host can only reach a public HTTPS URL, so HTTP-mode development means running behind a tunnel and pointing MCP_PUBLIC_URL at it.

bun run dev builds the widgets first: the server serves the built HTML from dist/widgets/, not the React source, so rebuild after touching anything under src/widgets/app/.

The widgets use React, TypeScript, Vite, Tailwind CSS, DaisyUI and Lucide. Vite produces one self-contained HTML resource per widget, so nothing needs hosting.

Local builds require Bun 1.3.3 and Node.js 22.12 or newer.

Layout

src/index.ts       HTTP server, OAuth protected-resource metadata, MCP transportsrc/local.ts       stdio entrypoint for local mode (personal API key)src/auth.ts        Bearer-token verification (RFC 9728 challenges)src/server.ts      Tool and resource registrationsrc/api.ts         Client for the Kamai MCP APIsrc/elements.ts    list_elements paging, filtering and result budgetingsrc/widgets/       Widget resources, CSP metadata and the React widget sources

Contributing

See CONTRIBUTING.md. Security issues go to the address in SECURITY.md, not to the issue tracker.

License

Apache-2.0. Copyright 2026 Kamai Enterprises LTD.

The Kamai name and logo are trademarks of Kamai Enterprises LTD and are not covered by the license.

Source: README.md at commit 0c8ee0f

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestSep 30, 2026