KAI now runs on the Deep Space MCP

Published 13 September 2026 As a project manager, I had to open the register and read it myself before I could answer a simple question about my own job, so I can now ask KAI and get the answer back off live project data. Before. KAI lived inside the platform on its own plumbing. The Deep Space MCP was a separate road you connected to from Claude Desktop or ChatGPT. Two paths to the same project data, built twice, drifting apart. KAI could talk about Deep Space. It could not read your job. After. KAI in the Deep Space web app now talks to your project over the same MCP server your external client connects to at mcp.deepspacesync.com. One connection layer, one permission model, one set of tools. What KAI can read, your Claude Desktop connection reads too, and the reverse. What it reaches today, read-only: The projects you can already see in your workspace Budget Register Purchase Order register Progress Claims to your client, and the Payment Schedules your client returns against them Progress Claims from your subcontractors Extensions of Time Why it matters. "What is committed against the budget on Albany" stops being a five-click errand and becomes a sentence. More to the point, it is the same answer whether it comes from KAI in the platform or from your own assistant on your laptop, because it is the same read of the same record. No export, no copy of the truth sitting in a chat window going stale. The Committed tile reads $765,000.00. So does KAI, in the same frame. Your help guides are searchable through the connection As a CA three weeks into a new platform, I had to go hunting for the right guide and then find the right page in it, so I can now just ask how something works and get the answer with the guide it came from. Before. The published guides existed. Finding the one you needed, and the page in it, was on you. After. Twenty-eight published Deep Space guides are indexed and searchable through the connection: the Commercial Module guide, WIP and earned margin, Xero end to end, Variations, Notice Platform, HSEQ, Document and Drawing Control, Timesheets, the Onboarding and Operations Manual, and the rest. Ask how retention gets released back to a subcontractor and KAI searches the actual documentation, names the guide and the page, and hands you a link that opens on that page. Why it matters. Configuration and workflow questions get answered where the work is happening, at 6am, without waiting on a reply. The guides also stay live, so a guide published today is indexed and answerable today. Connection access is gated on a real Deep Space role Connecting runs through OAuth against your own Deep Space login and checks a role before anything is served. Every module is scoped to your existing entitlements, and the whole connection is read-only. You see what you can already see in the platform, and nothing writes back. Ask KAI what it is connected to and it will tell you the workspace, the region, your role, and exactly which modules are on. KAI keeps track of its own tools mid-conversation Where KAI's available tools changed partway through a conversation, it kept working from the set it had at the start, and would decline work it had just been given the ability to do. It is now told when its tool set changes between turns, and the current set is restated on the latest turn. Long sessions stop degrading. Getting connected The connection is live in production. Point your AI application at https://mcp.deepspacesync.com/mcp, sign in with your own Deep Space login, and you are connected. Talk to your CS contact to have the connection role switched on for your users. Full walkthrough: KAI in Horizon, User Guide (v1.3) Something not landing the way you expected, or a register you want KAI to reach next? Tell us in the feedback portal. We read every one.