JDE Atina MCP Core Purchase Server
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"jde-atina": {
"url": "http://localhost:8080/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
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 ecommerce
A command line tool for setting up commercetools MCP server
Rent GPUs, robots, drones, and construction gear on RIGShare; also onboards equipment owners.
Electronic component sourcing, BOM management, and PCB design workflows.
Read-only merchant data from 8 Chinese e-commerce platforms: orders, products, after-sales, ads
MCP Security Weekly
Get CVE alerts and security updates for JDEAtinaMCPPurchaseServer and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The JDE MCP Server allows Claude (or any MCP-compatible AI assistant) to interact with JD Edwards EnterpriseOne data in natural language. Currently supported modules:
User (Claude.ai / Claude Desktop)
│
▼
Claude AI (MCP Client)
│ MCP over Streamable HTTP
▼
JDE MCP Server (this application, port 8080)
│ REST API calls
├──────────────────────────────┐
▼ ▼
Mulesoft Purchase API Mulesoft Sales Order API
(port 8081) (port 8083)
│ │
▼ ▼
JD Edwards EnterpriseOne JD Edwards EnterpriseOne
| 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) |
| Field | Value |
|---|---|
| Name | JDE Atina (or any descriptive label) |
| URL | https://<your-host>/mcp/message |
| Transport | SSE (Server-Sent Events) |
Local development with ngrok:
If running the server locally, expose it with:ngrok http 8080Then use the generated
https://<random>.ngrok-free.app/mcp/messageas the URL.
claude_desktop_config.json. Add the MCP server under mcpServers:{
"mcpServers": {
"jde-atina": {
"url": "http://localhost:8080/mcp"
}
}
}
If the server is remote or exposed via ngrok, replace the URL accordingly:
{ "mcpServers": { "jde-atina": { "url": "https://<your-host>/mcp" } } }
To avoid calling jde_login on every conversation, you can pass a JDE token directly in the Claude Desktop config using the headers field. The server will pick it up automatically:
{
"mcpServers": {
"jde-atina": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer <your-jde-token>"
}
}
}
}
With this configuration, all MCP tools work immediately without calling jde_login first. The server reads the Authorization header, stores the token for the session, and reuses it for all subsequen