JAMS JAX
by JAMS Software, LLC
AI for enterprise job scheduling that runs on your model, in your network, under your permissions
JAMS JAX is an AI agent built into the JAMS Web Client that finds jobs, troubleshoots failures and answers how-to questions in plain language, shipped alongside JAMS MCP, a Model Context Protocol connector that brings JAMS into Cursor, VS Code, Claude Code, Claude Desktop and Codex. It is aimed at IT operations and platform teams running enterprise workload automation who cannot send scheduling data to a third-party model.
JAMS Software made JAX and JAMS MCP generally available on July 24, 2026, bringing AI to enterprise job scheduling under an unusually strict control model. JAX is an AI agent embedded in the JAMS Web Client that finds jobs, diagnoses failures and answers how-to questions in plain language, with every response grounded in the JAMS user guide and checked against a built-in glossary rather than generated freely. JAMS MCP is a connector built on the open Model Context Protocol standard that exposes JAMS to the AI tools engineers already use — Cursor, VS Code with GitHub Copilot, Claude Code, Claude Desktop and Codex — so teams can query jobs, investigate failures and manage runs without leaving their editor. The governance model is the differentiator: both capabilities run inside the customer's own network and act as the signed-in user with that user's exact JAMS permissions, with no elevated AI service account. Reads flow freely while every write action pauses for explicit user approval, JAX acts only when asked, it does not learn between sessions, conversations are not retained on the server, and JAMS never trains on customer data. Operations are written to dedicated logs and changes are recorded in the standard JAMS audit trail. Customers choose which model runs — OpenAI, Anthropic or a local model executing entirely on the customer's own hardware — and both capabilities ship at no additional cost as part of JAMS Web. JAMS, founded in 1987 and headquartered in Middletown, Delaware, schedules workloads across SQL Server, Azure Data Factory, Airflow, SAP, JD Edwards and Banner.
At a Glance
- Category
- Automation & Workflows
- Pricing
- Contact for pricing
- Target Market
- CIOs, IT Operations Leaders, Enterprise Developers, Platform Engineering Teams, Workload Automation Administrators
- Founded
- 1987
- Headquarters
- Middletown, Delaware, United States
Key Features
- ✓JAX in-product AI agent
Finds jobs, troubleshoots failures and answers how-to questions in plain language, grounded in the JAMS user guide and checked against a built-in glossary.
- ✓JAMS MCP connector
An open Model Context Protocol connector that brings JAMS into Cursor, VS Code with Copilot, Claude Code, Claude Desktop and Codex.
- ✓Runs as the signed-in user
Every action executes under the user's exact JAMS permissions with no elevated AI account.
- ✓Approval-gated writes
Read operations proceed automatically while every write action pauses for the user's explicit approval before it runs.
- ✓Bring your own model
Customers choose OpenAI, Anthropic or a local model running entirely on their own hardware inside their own network.
- ✓No retention, no training
JAX does not learn between sessions, conversations are not retained on the server, and JAMS never trains on customer data.
Capabilities
Use Cases
- •Diagnose a failed overnight batch run
Ask JAX in plain language why a job failed and get an answer grounded in JAMS documentation instead of digging through logs manually.
- •Manage scheduling from the IDE
Use JAMS MCP to query jobs, investigate failures and manage runs directly from Cursor, VS Code with Copilot, Claude Code or Codex.
- •Air-gapped AI operations
Run the whole assistant on a local model inside the customer network so no scheduling or job data leaves the environment.
Ideal For
Best For
- ✓Troubleshooting failed batch jobs in plain language without leaving the scheduler
- ✓Bringing enterprise job scheduling into AI coding tools via MCP
- ✓Regulated IT teams that must keep AI inference and scheduling data inside their own network
Deployment
Market Analysis
Pros
- ✓Strict identity, approval and retention model answers most enterprise AI-governance objections up front
- ✓No additional licence cost on top of JAMS Web
- ✓MCP connector meets engineers inside the tools they already use
Cons
- ✗Only useful to organisations already running JAMS for workload automation
- ✗JAX is documentation-grounded and read-first by design, so it will not autonomously remediate
- ✗No published pricing for the underlying JAMS platform
Pricing
JAMS Web (JAX and JAMS MCP included)
Contact for pricing
- ✓JAX AI agent at no additional cost
- ✓JAMS MCP connector at no additional cost
- ✓Local or commercial model of the customer's choice
- ✓Runs inside the customer network
JAX and JAMS MCP ship at no additional cost as part of JAMS Web; JAMS itself is licensed commercially and does not publish rates.
Sources
This page was written from 2 sources, 1 on domains other than jamsscheduler.com.
Stay Ahead of the Curve
Weekly enterprise AI insights for technology leaders. No spam, no vendor pitches—unsubscribe anytime.
SubscribeRelated Products
Axle
Universal API and AI agents that automate property and casualty insurance verification, monitoring and updates
Skan AI
A context graph of how work actually gets done, so enterprise AI agents can execute against reality
Freehand
Autonomous AI agents that audit every supply-chain invoice, enforce the contract and settle the dispute
Saris
AI workflow agents that automate lending, compliance, and back-office work for banks and credit unions