SDK & CLI
MCP
Two different things: a governed MCP gateway your agents call their tools through, and an MCP server that lets an assistant read your workspace.
The governed MCP gateway
- One endpoint,
POST /api/v1/mcp, for any standard MCP client (Streamable HTTP), with a key bound to one agent, created in Agents › MCP tools. - An owner or admin keeps the catalogue: the servers, how Azoth authenticates to them — secrets encrypted, never sent to an agent — and the review of each tool with its reversibility. Only approved tools are exposed, and a changed definition goes back to review.
- Every tool call crosses the agent’s mandate and Azoth Guard; an irreversible or financial call waits for a person’s approval. Results are scanned and marked untrusted. No argument and no result is kept: the call is sealed with codes and a hash.
- Tools only for now: resources, prompts and sampling are not offered. The gateway is off unless the deployment turns it on (
FEATURE_MCP_GATEWAY).
URL https://www.azothos.ai/api/v1/mcp
Header Authorization: Bearer az_live_… # a key bound to one agent (Agents › MCP tools)The Azoth MCP server
@azothos/mcpis an MCP server with no dependency, open source under Apache-2.0: it runs on your computer with Node.js 18 or later, over stdio, and reads your workspace through an API key.- Its tools return the dashboard’s own figures: the mandates and who answers for a decision, the rules in force, blocked decisions, the applicable law, compliance coverage, the proof status, spend and footprint, and the support sources.
- Every tool reads, except those whose annotations say they record something:
azoth_export_dossier— each export is anchored, timestamped and sealed, as from Proof › Dossiers — and, in the full profile,azoth_preflightandazoth_compress. The assistant’s drafts are not offered: a draft needs a person on its screen to confirm it.
Install
The server is not published yet: its npm package and its Claude Desktop extension will be linked here once they are.
Profiles
public, the default: the mandates, the rules, the proof, spend and the support sources — the tools below.full, withAZOTH_MCP_PROFILE=full(the extension’s Full profile switch): also the optimisation and FinOps tools, the tools of features a deployment turns on, and the former tool names, kept for one version.- A tool outside the profile is not listed, and a call to it is refused, naming the profile that offers it.
azoth_spendSpend and budgets by mandate
azoth_block_decisionsBlocked decisions
azoth_unmandated_usesUnmandated AI uses
azoth_mandates_overviewMandates overview
azoth_accountabilityWho answers for a decision
azoth_journal_entrySealed decision
azoth_model_choiceWhy this model and region
azoth_proof_statusProof status
azoth_active_rulesRules in force
azoth_data_flowsData flows
azoth_applicable_lawApplicable law
azoth_regulatory_changesRegulatory changes
azoth_compliance_coverageCompliance coverage
azoth_evidence_summaryThis quarter's evidence
azoth_workspace_healthWorkspace health
azoth_footprintEnergy and carbon
azoth_support_docsSearch the documentation
azoth_support_changelogWhat changed in Azoth
azoth_support_statusService status
azoth_support_errorError code explained
azoth_journal_querySearch the decision journal
azoth_evidence_exportEvidence pack
azoth_export_dossierExport a verifiable dossier
azoth_system_modulesSystem modules
The API key
Create it in Settings › Access. Prefer a personal key with the read role, an expiry and only the scopes its profile needs:
public insights:read journal:read usage:read
full advisory:read agents:read insights:read journal:read policy:read usage:readMost tools of the public profile read the dashboard’s own functions: they need the Starter plan or above, and the workspace’s assistant turned on (Settings › Organization). A key never receives a member’s e-mail address.
Privacy
- The server keeps nothing on your computer and sends no telemetry.
- Each call sends the key and the tool’s arguments to
AZOTH_API_URL— Azoth’s service, or your own deployment — and to nothing else. The address must use HTTPS (plain HTTP only on your own computer), and no redirect is followed. - What a tool returns goes to your MCP client and the model it uses, under that client’s own privacy policy: ids, codes, counts, costs and the names your members gave — never a member’s e-mail address.
What Azoth keeps of these calls is described in its privacy policy.
The remote connector
The remote connector is not enabled on this deployment.