JDE MCP Server

A Model Context Protocol (MCP) server that exposes JD Edwards (JDE) purchase order approval workflows to AI assistants like Claude. It acts as a bridge between Claude and the JDE backend through a Mulesoft API layer.

Table of Contents

• Overview
• Architecture
• Prerequisites
• Configuration
• Authentication
• Available Tools
• Usage Examples
• Error Handling

Overview

The JDE MCP Server allows Claude (or any MCP-compatible AI assistant) to interact with JD Edwards EnterpriseOne purchase order data in natural language. Users can list pending POs, review their details, and approve or reject them — all from a conversational interface.

Architecture

User (Claude.ai)
      │
      ▼
Claude AI (MCP Client)
      │  MCP over HTTP (SSE)
      ▼
JDE MCP Server
https://<your-host>/mcp/message
      │  REST API calls
      ▼
Mulesoft API Layer
      │
      ▼
JD Edwards EnterpriseOne

Prerequisites

| Requirement | Details | |---|---| | MCP-compatible client | Claude.ai (Pro / Team / Enterprise) or any MCP client | | JDE credentials | A valid JDE username and password | | Network access | Client must be able to reach the MCP server URL | | Server runtime | The MCP server must be running and publicly reachable (e.g., via ngrok for local dev) |

Configuration

Adding the MCP Server to Claude.ai

1. Open Claude.ai and go to Settings → Integrations (or the Connectors section).
2. Click Add MCP Server.
3. Enter the server details:

| Field | Value | |---|---| | Name | JDE Atina (or any descriptive label) | | URL | https://<your-host>/mcp/message | | Transport | SSE (Server-Sent Events) |

4. Save and confirm the connection is active.

Local development with ngrok:
If running the server locally, expose it with:

ngrok http 3000

Then use the generated https://<random>.ngrok-free.app/mcp/message as the URL.

Authentication

Every session must begin with a login call. The server maintains a session token after authentication; all subsequent tool calls reuse it until the session expires.

Login Parameters

| Parameter | Type | Required | Description | |---|---|---|---| | user | string | ✅ | JDE username (e.g., JDOE) | | password | string | ✅ | JDE password |

Session Behavior

• Session expiry is returned in the login response (e.g., 2026-03-28T13:29:25Z).
• If any tool returns a session error, call jde_login again and retry the operation.
• Credentials are never stored or echoed back to the user.

Available Tools

1. jde_login

Authenticates the user against JDE via the Mulesoft API. Must be called before any other tool.

{
  "tool": "jde_login",
  "parameters": {
    "user": "JDOE",
    "password": "yourpassword"
  }
}

Returns: Confirmation of authenticated user and session expiry timestamp.

2. jde_list_pending_purchase_orders

Lists all purchase orders currently pending approval for the logged-in user.

{
  "tool": "jde_list_pending_purchase_orders",
  "parameters": {
    "limit": 10
  }
}

| Parameter | Type | Required | Default | Description | |---|---|---|---|---| | limit | integer | ❌ | 10 | Max number of POs to return |

Returns: Array of pending purchase orders with fields including:

| Field | Description | |---|---| | documentOrderTypeCode | PO type (e.g., OP) | | documentOrderInvoiceNumber | PO number (e.g., 5082) | | documentCompanyKeyOrderNo | Company key (e.g., 00001) | | documentSuffix | Suffix (e.g., 000) | | entityNameSupplier | Supplier name | | entityNameShipTo | Ship-to entity name | | amountGross | Total gross amount | | currencyCodeBase | Currency (e.g., USD) | | dateRequested | Request date | | dateTransaction | Transaction date | | `calcula

... View full README on GitHub