Kamai MCP server

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

With KAMAIQUERYTOOLS=on (see below):

listblueprints also takes includeinventory (with a project_id): what each blueprint contains.

listprojects, getproject, getblueprint, requestblueprintupload, finalizeblueprintupload, and with the query tools gettablerowelements and getelementoutlines, 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 install bun run build:widgets KAMAIAPIKEY=... MCPAPIBASE_URL=https://mcp-api.kamai.io bun run local

Claude Code:

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

Claude Desktop (claudedesktopconfig.json):

{ "mcpServers": { "kamai": { "command": "bun", "args": ["/path/to/kamai-mcp/src/local.ts"], "env": { "KAMAIAPIKEY": "...", "MCPAPIBASE_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 KAMAIQUERYTOOLS=on to the environment for the query tools.

Run the HTTP server

bun install cp .env.example .env bun run dev

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

Shortened. The full README is on GitHub.