Kamai

io.kamaiv1.0.0更新於 Sep 30, 2026

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

已驗證Streamable HTTP可網頁執行Data & AnalyticsFiles & StorageProductivity & Workflow

概覽

AI 產生的概覽

將助理連接到 Kamai 建築圖說專案，讓它能檢視圖說、數量與構件，並管理專案與上傳。

功能
提供用於 Kamai 建築圖說工作的工具與互動式小工具：檢視專案與圖說、以可排序表格顯示量測出的數量，並列出房間、牆體、門、窗、物件等逐構件資料列及其輪廓。它可以建立或重新命名專案，列出、檢視與取消處理工作，並處理圖說 PDF 上傳，包括匯入聊天訊息中附帶的 PDF。它也能在面板中開啟 Kamai 應用程式。
適用情境
當助理需要在 Kamai 中處理以 PDF 圖說為基礎的建築數量時使用：檢視專案、核對量測出的數量與構件、追蹤處理工作，或上傳新圖說。它鎖定 Kamai 使用者，而非一般文件處理。
執行需求
遠端端點 Bun 1.3.3 與 Node.js 22.12 以上版本在本機以 stdio 執行。本機模式需要在 KAMAI_API_KEY 中提供 Kamai 個人 API 金鑰，並在 MCP_API_BASE_URL 中提供 API 基礎網址。HTTP 模式需要 MCP_PUBLIC_URL、MCP_AUTH_ISSUER，以及選用的 MCP_AUTH_JWKS_URI、MCP_ACCEPTED_AUDIENCES、PORT 與 KAMAI_APP_ORIGINS，且需要能存取 Kamai 的 MCP API 與授權伺服器。
安裝前請注意
KAMAI_API_KEY 中的個人 API 金鑰會作為每次 API 呼叫的 bearer 送出，工具以該金鑰擁有者的身分執行，應視為機密。工具可以建立或重新命名專案、取消處理工作並上傳圖說 PDF，會變更 Kamai 帳戶中的資料。圖說內容與專案資料會傳送到 Kamai 的 API 與授權伺服器。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Kamai，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "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.

來源：README.md，提交 0c8ee0f

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v1.0.0最新Sep 30, 2026