Key concepts

An MCP Server is a service that implements the Model Context Protocol. MCP Servers are built by Infor application teams and provisioned through the Registry, delivered through BaaS, or created by customers and third parties.

In API Gateway, an MCP Server is represented by a registered endpoint that the gateway proxies. Designating that endpoint as an MCP Server tells the gateway to route MCP traffic to it, apply the MCP authorization model, and include it in metadata discovery.

The gateway does not convert a conventional API into an MCP Server. The target endpoint must already implement MCP.

An MCP Client is an application that connects to MCP Servers to discover and invoke tools. In the context of API Gateway, MCP Clients include:

• External tools, such as Kiro, Claude Desktop, Cursor, or any OAuth 2.1-compatible MCP Client
• Infor GenAI Agents, which are AI agents built in Infor GenAI Studio that use MCP tools

An MCP Client Authorized App is an authorized application type in API Gateway that is specifically designed for MCP Clients. It uses OAuth 2.1 with Proof Key for Code Exchange (PKCE) as a public client without a client secret. It also enables administrators to control which MCP Servers each client can access.

The Target Endpoint Description is the description configured for an MCP Server endpoint. It is required for MCP Server endpoints and serves as the tool description that AI agents use to understand what the tool does.

This value is used in the operationSummary field in metadata responses and in tool discovery in Infor GenAI Studio.

• Write clear, action-oriented descriptions. For example: Retrieves customer order history by date range and customer ID.
• If the description is missing when you enable MCP Server and attempt to save, the save is blocked and a validation error is displayed.
• Existing MCP endpoints without descriptions continue to function, but they do not appear in GenAI tool discovery until a description is added.