Designating endpoints as MCP Servers
Before you designate an endpoint as an MCP Server, ensure that:
- You are assigned the IONAPI-Administrator role.
- The
Enablemcpfornoninforfeature flag is enabled. This feature flag is enabled by default. - A Non-Infor API suite with at least one endpoint is configured.
- The target endpoint already implements the Model Context Protocol. Designating an endpoint as an MCP Server does not add MCP support to the endpoint.
Designating an endpoint as an MCP Server tells API Gateway that the target endpoint must be proxied, secured, and published as an MCP Server.
Only customer-created Non-Infor endpoints can be designated as MCP Servers in API Gateway. MCP configuration for other suite types is managed during provisioning or through the Registry.
| Suite type | Who configures MCP | Configuration location |
|---|---|---|
| Non-Infor (customer-created) | IONAPI-Administrator | Endpoint details page |
| Infor-Provisioned (Registry) | Configured centrally through the Registry | Read-only in API Gateway |
| Infor Non-Provisioned (Registry) | Configured centrally through the Registry | Read-only in API Gateway |
| Third Party (Registry) | Configured centrally through the Registry | Read-only in API Gateway |
| BaaS | Configured during BaaS provisioning | Read-only in API Gateway |
The endpoint is designated as an MCP Server and is discoverable as an MCP tool.
- An MCP icon on an API suite tile indicates that the suite contains at least one MCP-enabled endpoint.
- An MCP icon on an endpoint row indicates that the endpoint is an MCP Server.