Skip to main content The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery
Live 15 Actions

JD Edwards MCP Server
for AI Agents

Connect your AI agent to StackOne's JD Edwards MCP server and give it ready-to-use MCP tools out of the box. Auth, tool execution, and security all managed.

JD Edwards logo
JD Edwards MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

15 Agent Actions

Create, read, update, and delete across JD Edwards — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your JD Edwards MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every JD Edwards tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every JD Edwards call.

Tools Discovery →

What is the JD Edwards MCP Server?

A JD Edwards MCP server lets AI agents read and write JD Edwards data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's JD Edwards MCP server ships with pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All JD Edwards MCP Tools

Every action from JD Edwards's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Attachments

  • List Attachments

    List the media object attachments for an EnterpriseOne record.

Text Attachments

  • Get Text Attachment

    Get the text of the first text media object on an EnterpriseOne record.

Datas

  • Query Data

    Query or aggregate an EnterpriseOne table or business view via the AIS data service.

Execute Forms

  • Execute Form

    Execute an EnterpriseOne application form via the AIS form service.

Execute Batch Forms

  • Execute Batch Form

    Execute multiple EnterpriseOne forms in a single request via the AIS batch form service.

Messages

  • Send Message

    Send an EnterpriseOne message (PPAT) to external email or the Work Center.

Execute Orchestrations

  • Execute Orchestration

    Run a published EnterpriseOne orchestration by name via the AIS Orchestrator service.

All Orchestrations

  • Get All Orchestrations

    List the orchestrations available to the authenticated user via the discovery service.

Orchestrations

  • Get Orchestration

    Get the definition and expected inputs of a single orchestration.

Processing Options

  • Get Processing Options

    Retrieve the processing option values for an EnterpriseOne application and version.

Discover Reports

  • Discover Report

    Discover the details and configured overrides of an EnterpriseOne report (UBE).

Execute Reports

  • Execute Report

    Submit an EnterpriseOne report (UBE) for execution.

Report Status

  • Get Report Status

    Get the completion status of a submitted EnterpriseOne report (UBE).

Default Configs

  • Get Default Config

    Retrieve the AIS Server capabilities and default configuration.

Execute Watchlists

  • Execute Watchlist

    Execute an EnterpriseOne watchlist and return its current results.

JD Edwards AI Agent Use Cases

Connect your AI agent to JD Edwards and help your team scale the finance operations they run by hand today.

Invoice Processing

Automate invoice processing with AI agents connected to your ERP, accounting software, and AP tools through StackOne.

View
QuickBooks OnlineXeroNetSuiteSage IntacctBillFreshBooksWaveZoho Books
Accounts Receivable Dunning

Use StackOne to connect your AI agent to your accounting, CRM, and messaging systems to automate Accounts Receivable dunning and payment follow-up.

View
QuickBooksXeroFreshBooksStripePayPalSalesforceHubSpotGmail
Invoice Processing

Use StackOne to connect your AI agent to your accounting, email, and document management systems to automate invoice processing and purchase order matching.

View
QuickBooks OnlineXeroGmailOutlookGoogle DriveSharePointDropboxSlack

Set Up Your JD Edwards MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to JD Edwards in under 10 lines of code.

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More ERP / ITSM MCP Servers

JD Edwards MCP Server FAQ

Does StackOne have a JD Edwards MCP server?
Yes. StackOne offers a hosted JD Edwards MCP server, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
JD Edwards MCP server vs direct API integration — what's the difference?
A JD Edwards MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling JD Edwards. A JD Edwards MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling JD Edwards at runtime. StackOne provides both.
How does JD Edwards authentication work for AI agents?
JD Edwards authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own JD Edwards account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are JD Edwards MCP tools vulnerable to prompt injection?
Yes — JD Edwards MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a JD Edwards agent and how do I avoid it?
Context bloat happens when JD Edwards tool schemas and API responses eat your JD Edwards agent's memory, preventing it from reasoning effectively. A single JD Edwards query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my JD Edwards agent can access?
Yes — you can limit which actions your JD Edwards agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my JD Edwards MCP server?
Yes — you can create custom agent actions for your JD Edwards MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research JD Edwards's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a JD Edwards MCP server?
Skip a JD Edwards MCP server if your integration is purely software-to-software — direct JD Edwards API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call JD Edwards actions at runtime.
What AI frameworks and AI clients does the StackOne JD Edwards MCP server support?
The StackOne JD Edwards MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.