Kipso

An agent-native, owner-side construction PM demo. You drive it from Claude and watch it in the screens.

It runs on fictional data for Cedar Ridge Unified School District: three projects, three funding sources and three contractors, following the change-order-to-payment loop. "Today" is fixed at October 19, 2026.

Workspace owner: first-time setup with the owner key

The owner key opens the workspace so you can invite the first admin (Team screen). An admin can then turn the key off, and everyone signs in with email.

Connect it to Claude

  1. Sign in, open Team & security → Access tokens, and make a token. Your connector URL is https://demo.getkipso.com/t/<token>/mcp. What Claude does is recorded as you, and sensitive actions wait for you to confirm them in the app. (Before anyone signs in, the owner can use https://demo.getkipso.com/<owner key>/mcp.)
  2. In claude.ai, open Customize → Connectors (on some accounts it's Settings → Connectors), click +, and choose Add custom connector. On a Team or Enterprise plan, an org owner may have to add it.
  3. Name it Kipso, paste the URL, and click Add. Leave the OAuth fields empty.
  4. In a new chat, turn the connector on from the tools menu.

Try it

Keep the screens open in another tab, then ask Claude: "Run the Kipso morning walkthrough." Everything Claude does shows up in the screens' Activity rail within a few seconds. You can also ask: "What's our change-order exposure at Lincoln, and what should I do about pay app #7?"

Everyone in a workspace shares the same data, and changes persist between chats. To start over, ask Claude to run reset_demo, or click Reset demo data in the screens.