一个 stdio MCP 服务器，在 Azure Foundry 上包裹 Microsoft-Decision-1。代理使用一个 decide 工具进行快速、有界、经过模式验证的评估，无需生成或解析散文。

用于路由、分类、与所提供证据的验证、优先级排序和评分标准。它不是聊天模型、确定性规则引擎或授权服务。类型安全确保答案结构和标签的有效性，而非正确的判断。

布置

需要Node.js 22+ 和 Microsoft-Decision-1 部署。如果你是从 Azure 资源开始的，建议先从零开始执行部署 Microsoft-Decision-1。

运行npm包时，无需克隆或构建仓库：

使用 npx --yes @jonathanyee/[email protected] --help 查看无需 Azure 配置或推理请求的选项。该版本置顶以保证可复现性;升级时请有意更新。

如果您之前使用过无作用域的 ms-decision-mcp npm 包，请将安装和 MCP 客户端配置更新为 @jonathanyee/ms-decision-mcp。现有安装不会自动迁移。可执行文件仍名为 ms-decision-mcp。

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.