AI assistants

In the beta · tested with Claude Code

Connect an AI assistant to KitAxis

A connected AI assistant can work with your plans while you talk to it: draft and revise plans, record evidence and check readiness. It has been tested end to end with Claude Code; other assistants that support remote connectors over the Model Context Protocol (MCP) have not been tested yet. You approve the connection on a KitAxis page, and only you can sign a plan off.

How to connect

  1. Add KitAxis

    Add https://app.kitaxis.com/mcp as a remote MCP server in your assistant. For Claude Code, run claude mcp add --transport http --scope user kitaxis https://app.kitaxis.com/mcp in a terminal. Then start Claude Code, type /mcp, choose kitaxis and choose Authenticate.

  2. Approve it in KitAxis

    A KitAxis page opens. Sign in with your beta account, check the assistant’s name and where it sends you back to, and choose “Allow access”. Nothing is shared until you do. A name the assistant states about itself is marked “not verified”.

  3. Work in your conversations

    Ask the assistant to list your workspaces, draft a plan or record evidence. KitAxis checks your beta access on every request it makes.

  4. Disconnect any time

    In the web app, open “Connected assistants”, choose “Show connected assistants” and then “Disconnect” next to the assistant.

What an assistant can and can’t do

Your assistant does the thinking. KitAxis keeps the records and checks that the required evidence is recorded. It runs no AI models itself.

  • List and create workspaces and projects.
  • Create plans and save new revisions.
  • Record evidence against acceptance criteria.
  • Evaluate gates and read a plan’s status and readiness.
  • Export a plan.
  • It can never approve a plan or revoke an approval. Sign-off stays with you, in the web app, with your password.
  • It cannot cancel plans, delete anything, change your account, or see anyone else’s workspaces.
  • It can mark a gate not applicable, with a written reason, without asking you. That counts toward “ready” without evidence.
  • It can save a revision that lowers the plan’s level without asking you.
  • Ready means complete and evidenced for this revision; not execution approval. KitAxis never runs a plan.
  • Connecting with full access gives it every ability listed above.
  • What it records is saved under your account, not under the assistant’s name. Evidence it records is client-reported; not independently verified by KitAxis.

Tested so far

Claude Code was tested end to end on 28 September 2026, against the live service: connecting, approving the connection, and a full planning run from a new project to a plan showing Ready, then its export.

Other assistants that support remote MCP connectors may connect the same way, but we have not tested them end to end yet. Each one is added here once a live connection passes.

Access tokens last 15 minutes and work only for the KitAxis connection address. The assistant stays connected by renewing them, and each renewal replaces the one before. If your beta access ends, every connected assistant loses access at once.

KitAxis is independent of, and not endorsed by, Anthropic, OpenAI or any AI assistant provider.

Plan with KitAxis today

Plans, evidence and readiness work in the web app and through a connected assistant. Sign-off happens only in the web app, with your password. Ask for an invite to the free beta.