01 Assistants
Claude Code and MCP
Use local skills for engineering and Hosted preview tools for authorised status reads.
Separate authoring from asking about status
An assistant can participate in two distinct workflows. Local skills help you model, build, query, report and qualify within an approved project. Hosted MCP lets an authorised assistant read bounded qualification metadata from the protected preview. MCP is the Model Context Protocol connection used to expose those tools.
Neither workflow gives the assistant authority to decide your fact grain, invent an oracle or approve an external write. Connecting an assistant to Hosted also does not install the local core or provide the retained private evidence needed for numerical qualification.
Use local skills for a bounded engineering task
With an approved installation, invoke the Analytical Spine front door explicitly. Claude Code supports the short or namespaced form:
/analytics-spine/analytics-spine:analytics-spineGive the assistant a specific task and a stopping point. Ask it to explain missing evidence, prepare a model draft or show a deployment plan. Review source-read requests and digest-bound target writes at the relevant boundary. Installation is not blanket permission to execute every later step.
Keep client values out of learning prompts. An external provider has its own processing controls. The Hosted ledger's value-free upload contract does not describe everything an assistant might read locally or receive in chat.
Use five read-only Hosted tool categories
The preview service exposes five bounded MCP tools for authorised reads. The categories below describe their purpose; they are not new shell commands or a public connection endpoint.
| Read | Purpose |
|---|---|
| Organisation | Read the authorised organisation context. |
| Project | Read projects within the current grants. |
| Qualification | Inspect scoped qualification metadata and freshness. |
| Attestation | Read authorised signed-claim information and history. |
| Certification summary | Read a summary only when approved real certificate bindings exist; otherwise unavailable. |
Current membership, exact action and project grants, terms and quotas matter. An OAuth scope, subscription or role alone does not grant project access. Value-free output checks constrain what the service can disclose. The tools do not expose raw oracle numbers, SQL, DAX, local receipts or report images.
Connection remains protected preview
Claude Code connection instructions use the configured Entra protected-preview flow. That support is distinct from a completed real-host walkthrough. Obtain the approved connection details through the preview's authorised process. This guide intentionally publishes no internal endpoint or operational identity.
Packaging for ChatGPT, Codex and Microsoft 365 is also preview work. Prepared channel bundles do not establish approved listings or completed sign-in journeys. Do not treat the existence of a connector package as general production availability.
Ask questions that preserve the scope
Useful requests include: “What is the latest state for the project I can access?”, “When was this qualification observed, and when does it expire?” and “Which declared scope does this attestation cover?” Ask the assistant to report unknown, expired or unavailable states explicitly.
Avoid asking it to infer an organisation identifier, broaden a project grant or describe a certificate that has not been authorised. For local diagnostics, return to the retained evidence through its owning workflow. Read Evidence and receipts for the difference between the local proof, value-free attestation and signed acknowledgement.