An MCP Server enabling integration with IBM Decision Server Runtime to retrieve and invoke decision services.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"ibm-odm-decision-mcp-server": {
"env": {
"ODM_PASSWORD": "odmAdmin"
},
"args": [
"--from",
"git+https://github.com/DecisionsDev/ibm-odm-decision-mcp-server",
"start",
"--url",
"https://odm-res-console-url",
"--ssl-cert-path",
"certificate-file",
"--username",
"your-username"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The IBM ODM Decision MCP Server bridges IBM ODM with modern AI assistants and orchestration platforms. - Expose decisions as tools for AI assistants - Automate decisions dynamically in workflows - Integrate easily with Watson Orchestrate, Claude Desktop, and Cursor AI - Centralize and expose business logic to end users and bots
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'uv' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
uv is vulnerable to arbitrary file write through entry point names
### Impact In versions of uv prior to 0.11.15, when installing a distribution containing an entry point specification (under `console_scripts` or `gui_scripts`), uv would place the generated entry point according to the given name even if doing so resulted in a path outside of the environment's scripts directory. A malicious wheel could use this to place an executable outside of the intended environment, including in a directory already present on the user's `PATH`. This could shadow or overwr
uv vulnerable to arbitrary file deletion through RECORD entries
## Impact Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall. uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall. uv does not use the RECORD fi
uv allows ZIP payload obfuscation through parsing differentials
### Impact In versions 0.9.5 and earlier of uv, ZIP archives were handled in a manner that enabled two parsing differentials against other components of the Python packaging ecosystem: 1. Central directory entries in a ZIP archive can contain comment fields. However, uv would assume that these fields were not present, since they aren't widely used. Consequently, a ZIP archive could be constructed where uv would interpret the contents of a central directory comment field as ZIP control structur
uv has differential in tar extraction with PAX headers
### Impact In versions 0.9.4 and earlier of uv, tar archives containing PAX headers with file size overrides were not handled properly. As a result, an attacker could contrive a source distribution (as a tar archive) that would extract differently when installed via uv versus other Python package installers. The underlying parsing differential here originates with astral-tokio-tar, which disclosed this vulnerability as CVE-2025-62518. In practice, the impact of this vulnerability is **low**:
uv allows ZIP payload obfuscation through parsing differentials
## Impact In versions 0.8.5 and earlier of uv, remote ZIP archives were handled in a streamwise fashion, and file entries were not reconciled against the archive's central directory. This enabled two parser differentials against other Python package installers: 1. An attacker could contrive a ZIP archive that would extract with legitimate contents on some package installers, and malicious contents on others due to multiple local file entries. The attacker could choose which installer to target
Click any tool to inspect its schema.
odm_decisionsIBM ODM decisions and rulesets available for execution
odm://decisions/{decision_name}
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Manage Supabase projects — databases, auth, storage, and edge functions
Copy/paste detector for programming source code, supports 223 formats. AI-ready with token-efficient reporter, skill and MCP server.
MCP Security Weekly
Get CVE alerts and security updates for Ibm Odm Decision Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The IBM ODM Decision MCP Server bridges IBM ODM with modern AI assistants and orchestration platforms.
It enables you to:
Check the Claude Desktop Integration Guide for detailed instructions on setting up and using the Decision MCP Server in Claude Desktop.
Or check the IBM Bob Integration Guide for detailed instructions on setting up and using the Decision MCP Server in IBM Bob.
Watch our demo video to see Claude Desktop integration in action:
https://github.com/user-attachments/assets/53e9f887-6972-40d9-81c0-51dd4b31b165
IBM watsonx Orchestrate can be augmented with decisions implemented in IBM Operational Decision Manager (ODM) thanks to the Decision MCP Server.
For detailed instructions, see the IBM watsonx Orchestrate Integration Guide.
The easiest way to run the Decision MCP Server is using uv, which handles package installation and execution:
macOS and Linux:
curl -LsSf https://astral.sh/uv/install.sh | sh
Windows:
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
Alternative (via pip):
pip install uv
For more installation options, see the uv documentation.
Once uv is installed, you can run the Decision MCP Server directly without manual installation:
uvx --from git+https://github.com/DecisionsDev/ibm-odm-decision-mcp-server start --url http://localhost:9060/res
The uvx command automatically:
Depending on your IBM ODM deployment, use the appropriate authentication/authorization method:
--zenapikey <your-zen-api-key>ZENAPIKEY=<your-zen-api-key>--username <user> --password <pass>ODM_USERNAME=<user> ODM_PASSWORD=<pass>--client-id <CLIENT_ID> --client-secret <CLIENT_SECRET> --token-url <TOKEN_URL> and optionally --scope <scope>CLIENT_ID=<client_id> CLIENT_SECRET=<client_secret> TOKEN_URL=<URL> and optionally SCOPE=<scope>--client-id <CLIENT_ID> --pkjwt-key-path <PRIVATE_KEY_PATH> --pkjwt-cert-path <CERT_PATH> --token-url <TOKEN_URL> and optionally --scope <scope> and --pkjwt-key-password <PASSWORD> if the private key is password-protected.