Choose OpenEdge MCP Server when you need to:
  • Expose existing OpenEdge or REST APIs to LLM agents rapidly with strong safety controls.
  • Enforce structured discovery and execution by applying scope-based routing and disciplined policies from the start.
  • Deliver reproducible, attestable MCP surfaces ideal for regulated or multi-tenant environments requiring predictable deployments.
  • Operate under strict security requirements by supporting TLS/mTLS, token rotation, and JWKS for hardened transport and identity assurance.
Avoid using OpenEdge MCP Server if:
  • You require dynamic code or tool generation beyond the OpenAPI and prompt model.
  • You need a full policy engine. OpenEdge MCPServer provides scopes and routing only.
  • You expect the server to issue identity tokens. Token management must be delegated to your identity provider.