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