Kamai

io.kamaiPublished by kamai.ioOfficial publisherv1.0.0Updated Oct 28, 2026

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

VerifiedStreamable HTTPWeb executableFiles & Storage Data & Analytics Media & Design

Server details

Identifier: io.kamai/mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 30, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to kamai.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.kamai%2Fmcp.svg)](https://sourceweft.com/mcp/io.kamai%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Kamai's remote MCP server lets an assistant browse construction-blueprint projects, inspect takeoff quantities and elements, and edit or upload blueprints.

What you can do: Browse projects and blueprints, with ids, readiness and per-blueprint inventory
View blueprint pages with takeoff shapes, element outlines, legend folders and sortable quantity tables
Download a processed blueprint PDF with detected elements highlighted
Edit elements (rename, recolour, refile), create folders, set opening heights, create or rename projects
Manage processing jobs and upload blueprint PDFs, including a PDF attached to a chat message
With query tools enabled: count and find elements, compute net wall surface area, set drawing scale or rotation, render linked tables
When to use it: Useful when you work with Kamai construction takeoffs and want an assistant to look up quantities, inspect blueprint elements, or make small edits and uploads without switching to the Kamai app.
Requirements: Remote endpoint at mcp.kamai.io with OAuth sign-in required. The README also documents a local stdio mode using a personal Kamai API key (KAMAI_API_KEY) and Bun 1.3.3 with Node.js 22.12 or newer for local builds. Query tools need KAMAI_QUERY_TOOLS=on.

Before you install

Tools can change data: elements are renamed, recoloured and refiled, folders and projects are created or renamed, opening heights and drawing scale are stored, and jobs can be cancelled. Uploads and downloads move blueprint PDFs. A personal API key acts as its owner for every call, so treat it as a secret. Blueprint data is sent to Kamai's API.

Installation

In SourceWeft

Open Kamai in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.kamai%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "kamai": {
      "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

Tool	What it does
`view_projects`	Interactive panel of the user's projects and blueprints
`list_blueprints`	Blueprints grouped by project, with their ids and whether they are ready
`view_blueprint`	A blueprint page with its take-off shapes drawn on top
`view_takeoff`	Measured take-off quantities as a sortable table
`list_elements`	Per-element rows (rooms, walls, doors, windows, objects) with outlines
`list_folders`	A blueprint's legend folders
`download_plan`	A PDF of a processed blueprint with its detected elements highlighted, as a temporary download link
`update_elements`, `move_elements`, `create_folder`	Rename, recolour and refile elements; create a folder
`set_opening_height`	Store a user-stated height, or a door/window tag, on wall-surface opening pieces
`create_project`, `update_project`	Create or rename a project
`list_jobs`, `get_job`, `cancel_job`	Processing jobs of a project
`view_upload`	Upload panel for a blueprint PDF
`ingest_blueprint_from_chat`	Import a PDF attached to a ChatGPT message (ChatGPT only)
`open_kamai`	Open the Kamai app in a panel

With KAMAI_QUERY_TOOLS=on (see below):

Tool	What it does
`count_elements`	Counts and totals by Kamai category (doors, windows, walls, wet rooms…), grouped, summed in the database
`find_elements`	Individual elements with type, folder, tag, handing and measurements
`calculate_wall_surface_area`	Net wall (paint or plaster) area of rooms
`render_table`	A table panel whose rows highlight their elements on the plan
`set_scale`	Set a blueprint's drawing scale
`set_rotation`	Turn how a blueprint is shown (display only)

With KAMAI_HOST_PROBE on (the default on dev and debug, off in prod; see below):

list_blueprints also takes include_inventory (with a project_id): what each blueprint contains.

list_projects, get_project, get_blueprint, request_blueprint_upload, finalize_blueprint_upload, and with the query tools get_table_row_elements and get_element_outlines, and with the probe report_host_probe, 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

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 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" } } } }

{ "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. Add KAMAI_QUERY_TOOLS=on to the environment for the query tools.

Run the HTTP server

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.

Variable	Meaning
`PORT`	Listen port, default 8006
`MCP_PUBLIC_URL`	The URL hosts call and ask a token for (the `resource` in discovery); a tunnel, not `localhost`
`MCP_AUTH_ISSUER`	Issuer of the access tokens, matched byte for byte against the token's `iss`
`MCP_AUTH_JWKS_URI`	Optional. Defaults to `{MCP_AUTH_ISSUER}/jwks.json`
`MCP_API_BASE_URL`	Kamai MCP API base URL, `https://mcp-api.kamai.io`. Also the audience an access token must carry
`MCP_ACCEPTED_AUDIENCES`	Optional comma-separated audiences, for a cutover. Defaults to `MCP_API_BASE_URL`
`KAMAI_API_KEY`	Local mode only: the personal API key the tools run as
`KAMAI_APP_ORIGINS`	Optional comma-separated extra origins `open_kamai` may frame; the first becomes the default
`KAMAI_QUERY_TOOLS`	`on` registers the query tools. Only once the API layer serves `/v1/vocabulary` (401, not 404)
`KAMAI_ROTATION`	`off` drops `set_rotation` from the query tools (on by default; needs an API layer that serves `PUT .../blueprints/{id}/rotation`)
`KAMAI_HOST_PROBE`	`on` or `off` registers `probe_host` and `report_host_probe`. Unset, it is on when Cloud Run's `K_SERVICE` starts with `dev-` or `debug-`, off otherwise. Never in local mode
`KAMAI_MCP_NO_INSTRUCTIONS`	`1` leaves the server instructions out, as claude.ai does; for evals

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/errors.ts      The text a failed tool call shows the modelsrc/query/         Query tools: descriptions, vocabulary, filters, budgets, contractsrc/widgets/       Widget resources, CSP metadata and the React widget sourcesscripts/           Widget build (escapes & so Open WebUI can embed the                   widgets); check-routes and check-vocabulary against a live APIscripts/open-webui/                   Open WebUI helpers: an open_kamai Tool, a display-mode                   host script, a local bridge demo

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/errors.ts      The text a failed tool call shows the modelsrc/query/         Query tools: descriptions, vocabulary, filters, budgets, contractsrc/widgets/       Widget resources, CSP metadata and the React widget sourcesscripts/           Widget build (escapes & so Open WebUI can embed the                   widgets); check-routes and check-vocabulary against a live APIscripts/open-webui/                   Open WebUI helpers: an open_kamai Tool, a display-mode                   host script, a local bridge demo

Privacy and support

Privacy policy: https://kamai.io/privacy-policy
Support: https://kamai.io/support or [email protected]

Contributing

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

License

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

Source: README.md at commit b4bacc1

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestSep 30, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts