Connecting external MCP Clients

Any OAuth 2.1-compatible MCP Client can connect to MCP Servers through API Gateway. The authentication flow is the same for all clients, but the configuration method depends on the client.

Before you configure a client, create an MCP Client authorized app as described in Creating MCP Client authorized apps.

Setting up Kiro

Use the configuration generated for the MCP Client authorized app to connect Kiro to the selected MCP Servers.

When you create the authorized app, specify the redirect URL provided during Kiro setup. The URL is typically in this format:

http://localhost:{port}/callback

In your Kiro project, create or edit this file:
```
.kiro/settings/mcp.json
```

Paste the generated MCP Client configuration into the file.

For example:

{
							"mcpServers": {
							"infor-m3-api": {
							"type": "http",
							"url": "https://mingle-ionapi.inforcloudsuite.com/ionapi/MYTENANT/M3/mcp/",
							"oauth": {
							"clientId": "MYTENANT~EbTQ-u7A7OfTqrGMlrtVK-7wBeddA5qUWw7OrroXY7g"
							}
							}
							}
							}

Save the file.
Invoke an MCP tool in Kiro.

When you invoke an MCP tool for the first time, Kiro opens a browser window for Infor authentication.
Sign in with your Infor credentials and grant consent.

The MCP tools are available in your Kiro session.

Setting up Claude Desktop

Use the configuration generated for the MCP Client authorized app to connect Claude Desktop to the selected MCP Servers.

When you create the authorized app, specify a redirect URL in this format:

http://127.0.0.1:{port}/oauth/callback

Open the Claude Desktop configuration file:
```
claude_desktop_config.json
```
Paste the generated MCP Client configuration into the file.
Save the file.
Restart Claude Desktop.
Use an MCP tool in Claude Desktop.

Claude Desktop opens a browser window and prompts you to authenticate when it accesses an MCP tool for the first time.
Sign in with your Infor credentials and grant consent.

Claude Desktop can access the MCP Servers selected for the authorized app.

Setting up other MCP Clients

Other OAuth 2.1-compatible MCP Clients, including Cursor and custom applications, can connect to MCP Servers through API Gateway.

The client must support OAuth 2.1 with PKCE, Protected Resource Metadata discovery, and standard MCP HTTP transport.

Setting up Cursor

Use the configuration generated for the MCP Client authorized app and adapt it to the MCP configuration format supported by Cursor.

Open the MCP configuration in Cursor.
Add the MCP Server configuration generated by API Gateway.

Ensure that the configuration contains the MCP Server URL and the generated OAuth client ID.
Save the configuration.
Use an MCP tool in Cursor.

Cursor prompts you to authenticate through a browser when authorization is required.
Sign in with your Infor credentials and grant consent.

Cursor can access the MCP Servers selected for the authorized app.

Setting up custom OAuth 2.1-compatible MCP Clients

A custom MCP Client can connect to API Gateway when it supports these requirements:

OAuth 2.1 with PKCE by using the authorization code flow as a public client
Protected Resource Metadata discovery through .well-known/oauth-protected-resource
Standard MCP HTTP transport

Adapt the generated MCP Client configuration to the configuration format used by your application.

Include the full proxy URL for each MCP Server and the generated OAuth client ID.
Configure the application to read the Protected Resource Metadata document when it receives an HTTP 401 response.
Configure the application to start the OAuth 2.1 authorization code flow with PKCE.
Use the access token returned by the authorization server for MCP tool calls.

The custom client can discover the authorization server, authenticate users, and access the MCP Servers selected for the authorized app.