Give EnterpriseOne a standard tool interface for AI.
Use Model Context Protocol to expose governed JD Edwards metadata, Orchestrations and related tools to AI clients through standard interfaces.
MCP does not replace AIS or Orchestrations. It gives AI clients a standard way to discover and call the capabilities that sit behind them.
What belongs behind MCP
- JDE Orchestration discovery and execution
- authoritative JDE metadata
- read-only file/log investigation
- bounded cross-system Compositions
Why the gateway matters
Local STDIO MCP servers are convenient and simple, but enterprise AI clients may be remote. Steward can expose compatible tool-oriented STDIO servers through an authenticated HTTP edge, with explicit backend configuration, agent restrictions, audit and user-bound access to supported AD resources.
Keep the tool small
The safest MCP server is often a narrow one. An agent that receives ten precise business tools is easier to govern than one that receives a generic shell, database or arbitrary API surface.
Related MCP resources
See the JDE Metadata MCP Server for authoritative JDE schema facts, Steward for secure remote access to compatible MCP tools, and MCP for JDE for the architectural background.