INITE Process Diagnostic MCP server

INITE Diagnostic — a process audit your agent can run

Point an assistant at a business process and get back what it costs today, where it breaks first, and what to automate next.

> Our WhatsApp enquiries take until morning to answer. Is that worth fixing?

  start_audit(language: "en")        → audit_token: 9f2c…, first question
  answer_audit(field: "channels", value: "whatsapp, instagram")
  answer_audit(field: "dailyInquiries", value: "50-100")
  …
  answer_audit(finish: true)         → findings

It is the same audit that runs at inite.solutions/en/audit.

Two depths

Free — eight questions about one process. Pick the thing your people still do by hand. The interview maps it and says what it costs now and what changes if it runs itself. No account needed in the browser; from an agent, the interview and the arithmetic need none either — see Works before you sign in — and the reading itself needs one.

Premium — forty-three slots across the whole business, grouped into strategy, marketing, operations, finance and technology. The interview has a budget of thirty-five questions against those forty-three slots, so it must leave some unasked, and choosing which is the part worth having a model for. It routes by the share of each area still open, not by the count, so one expert cannot conduct two thirds of the conversation.

The first eight slots of a premium run are the free eight, unchanged. An audit that upgrades mid-way is not asked them twice.

Works before you sign in

Two of the tools run entirely on your machine. No account, no allowance, no call home.

diagnosticquestions hands over the interview itself — the eight things a diagnostic has to establish, in the words they are asked in — and your assistant conducts it, in the person's own language, with options that look like their industry. readanswers then does the arithmetic on what came back.

> Eighty enquiries a day between the two of us, mostly WhatsApp, kept in a spreadsheet.

  read_answers(answers: {...})

  From what you have been told:
    80 enquiries a day across 2 people — 40 each.
    12 of them become leads — 15% of what arrives.
    3 channels enquiries arrive on. The record of them: a spreadsheet.

  That is the arithmetic. What it cannot do is say what to automate first.

The split falls where the competences do. A model conducts an interview far better than it divides eighty by two and remembers what the range said, so the caller asks and this counts — and every assumption it had to make is printed beside the result ("read 50-100 as 75").

Signing in adds the audit itself: the next question chosen from everything already said, the findings written against them, a run saved under your account that you can come back to, and the forty-three question depth.

Install

Claude Desktop, Cursor, or any client that launches a stdio server:

{
  "mcpServers": {
    "inite-diagnostic": {
      "command": "npx",
      "args": ["-y", "@inite/diagnostic"]
    }
  }
}

Then, when you want the audit rather than the arithmetic:

npx @inite/diagnostic login

That opens a browser, you approve, and the token is stored at ~/.config/inite/mcp-diagnostic.json with owner-only permissions. Authorization code with PKCE over a loopback redirect, the flow RFC 8252 prescribes for a native app. Nothing is written to the repository and no secret ships in the package.

Its own file, not the one @inite/visibility writes. Both tokens are issued by the same authorization server and belong to the same person, and neither works in the other's place: RFC 8707 binds each one to the resource it was asked for. Sharing a file would mean the second login silently replaced the first one's token with something that 401s. For the same reason this package reads INITEDIAGNOSTICTOKEN before INITE_TOKEN.

Tools

Shortened. The full README is on GitHub.