Decision API for agents

A stdio MCP server wrapping Microsoft-Decision-1 on Azure Foundry. Agents use one decide tool to make fast, bounded, schema-validated evaluations without generating or parsing prose.

Use it for routing, classification, verification against supplied evidence, prioritization, and rubric grading. It is not a chat model, deterministic rules engine, or authorization service. Type safety ensures valid answer structure and labels, not correct judgments.

Setup

Requires Node.js 22+ and a Microsoft-Decision-1 deployment. If you are starting without Azure resources, follow Deploy Microsoft-Decision-1 from scratch first.

Run the npm package without cloning or building the repository:

export AZURE_DECISION_ENDPOINT=https://your-resource.services.ai.azure.com
export AZURE_DECISION_DEPLOYMENT=your-deployment-name
export AZURE_DECISION_AUTH=azure-cli
az login
npx --yes @jonathanyee/[email protected]

Use npx --yes @jonathanyee/[email protected] --help to view options without Azure configuration or an inference request. The version is pinned for reproducibility; update it deliberately when upgrading.

If you previously used the unscoped ms-decision-mcp npm package, update your installation and MCP client configuration to @jonathanyee/ms-decision-mcp. Existing installations are not migrated automatically. The executable remains named ms-decision-mcp.

For a source checkout, install dependencies and build before launching:

The source setup below uses your normal Azure CLI profile. To keep that profile unchanged, run the build commands and set the endpoint/deployment variables below, but replace the bare az login and npm start commands with the login and launch commands in Dedicated Azure CLI login. The same profile isolation works with npx: prefix it with AZURE_CONFIG_DIR="$HOME/.azure-ms-decision".

npm install
npm run build

export AZURE_DECISION_ENDPOINT=https://your-resource.services.ai.azure.com
export AZURE_DECISION_DEPLOYMENT=your-deployment-name
export AZURE_DECISION_AUTH=azure-cli
az login
npm start

The endpoint must be the resource base URL, not a Foundry project endpoint. The server appends /providers/microsoft/v1/systemone. The request model is your deployment name; the response identifies the underlying model.

Deploy Microsoft-Decision-1 from scratch

This walkthrough uses the Foundry portal to create the resource and project, then deploys the model. You do not need Python or an Azure SDK to use this MCP server.