Troubleshooting

Use these troubleshooting tips to diagnose and resolve common issues with MCP Server and MCP Client configuration.

MCP endpoint not appearing in GenAI tools

  • Verify that the endpoint has a Target Endpoint Description.
  • Verify that the MCP Server toggle is enabled.
  • Call /ionapi/metadata/v1/{tenant}/operations?includemcp=true to confirm that the endpoint appears in the response.
  • Verify that metadata indexing has completed. Changes are typically reflected within seconds.

MCP Client cannot connect

  • Verify that the redirect URL in the authorized app matches the client callback URL exactly.
  • Verify that the EnableIONAPIMCPClient feature flag is enabled for the tenant.
  • Verify that the MCP Servers selected in the authorized app are currently MCP-enabled endpoints.
  • Verify that the Client ID in the client configuration matches the Client ID generated by API Gateway.

403 error when calling an MCP endpoint

  • Verify that the MCP Client authorized app is authorized for the MCP Server.
  • Edit the MCP Client authorized app and add the target MCP Server to the allowed server list. Up to 10 MCP Servers can be associated with an authorized app.

401 error with WWW-Authenticate header

  • This is expected behavior for the OAuth 2.1 discovery flow.
  • The MCP client should automatically handle this response by reading the Protected Resource Metadata and initiating the OAuth flow.
  • If you use a custom client, ensure that it supports the .well-known/oauth-protected-resource discovery mechanism.

MCP Server toggle not visible

  • Verify that the Enablemcpfornoninfor feature flag is enabled for the tenant.
  • For Infor-Provisioned, Non-Provisioned, Third Party, and BaaS suites, MCP status is managed through the Registry and might be displayed as a read-only indicator instead of a toggle.