Connecting MCP Clients

MCP clients connect to AireGlu MCP servers over HTTP using the Streamable HTTP transport with OAuth 2.0 authentication. This page covers how to obtain the connection configuration and set up common MCP clients.

Connection URI

Every MCP server has a connection URI in the format:

https://<runtime-host>/mcp/<tenancy>/<server-name>

To target a specific version:

https://<runtime-host>/mcp/<tenancy>/<server-name>/<version>

If no version is specified, the server's default version is used.

Copying the Connection URI

1. Navigate to AI Tools > MCP Servers
2. Click the three-dot menu on the server row
3. Select Copy URL

The URI is copied to your clipboard.

Copy Client Config

AireGlu generates a ready-to-use client configuration block for MCP-compatible clients. This is the fastest way to connect.

1. Click the three-dot menu on the server row (or a specific version row)
2. Select Copy Client Config
3. Paste the configuration into your client's config file

The generated configuration uses the mcp-remote proxy and includes the OAuth client details:

{
	"mcpServers": {
		"<server-name>": {
			"command": "mcp-remote",
			"args": [
				"https://<runtime-host>/mcp/<tenancy>/<server-name>",
				"2292",
				"--static-oauth-client-info",
				"{\"client_id\":\"<client-id>\",\"scope\":\"AireGluMcp\"}",
				"--timeout",
				"300"
			]
		}
	}
}

TIP

Version-specific configs are available from the three-dot menu on individual version rows within the expanded server list.

Authentication

AireGlu MCP servers use OAuth 2.0 for authentication. The authentication flow is handled automatically by the mcp-remote proxy.

How It Works

1. The MCP client discovers the OAuth metadata via the /.well-known/oauth-protected-resource endpoint
2. The client obtains a JWT token from the authorization server
3. The token is included as a Bearer token in subsequent MCP requests
4. AireGlu validates the token and extracts the user identity

The required OAuth scope is AireGluMcp.

First Connection

On first connection, mcp-remote opens a browser window for you to authenticate. After successful authentication, the token is cached locally and reused for subsequent connections.

Client Setup Guides

Claude Desktop

1. Copy the client config from AireGlu (see above)
2. Open Claude Desktop settings
3. Navigate to the MCP servers configuration (Developer > Edit Config)
4. Open the claude_desktop_config.json file
5. Merge the copied configuration into the mcpServers object
6. Save and restart Claude Desktop

Cursor

1. Copy the client config from AireGlu
2. Open Cursor settings
3. Navigate to MCP settings
4. Add a new MCP server using the copied configuration
5. Save and restart Cursor

Claude Code

1. Copy the client config from AireGlu
2. Add the server to your project's .mcp.json or global MCP configuration
3. Restart the Claude Code session

Prerequisites

All clients require mcp-remote to be installed. It is an npm package that acts as a local proxy bridging stdio-based MCP clients to remote HTTP servers with OAuth support.

Install it globally:

npm install -g mcp-remote

Or use npx (no installation required) - the generated config works with npx by replacing "command": "mcp-remote" with "command": "npx" and prepending "mcp-remote" to the args array:

{
	"mcpServers": {
		"<server-name>": {
			"command": "npx",
			"args": [
				"mcp-remote",
				"https://<runtime-host>/mcp/<tenancy>/<server-name>",
				"2292",
				"--static-oauth-client-info",
				"{\"client_id\":\"<client-id>\",\"scope\":\"AireGluMcp\"}",
				"--timeout",
				"300"
			]
		}
	}
}

Troubleshooting

Issue	Cause	Fix
Connection refused	Server or version is inactive	Check the Active toggle on both the server and version
401 Unauthorized	Invalid or expired token	Re-authenticate by removing cached credentials and reconnecting
405 Method Not Allowed	Client attempted SSE connection	Ensure your client uses Streamable HTTP transport, not SSE. AireGlu only supports HTTP POST for MCP requests
Tool/resource not found	Endpoint is inactive or misconfigured	Check the endpoint is active and the target endpoint still exists
No tools listed	Version has no active endpoints	Add and activate at least one endpoint in the version configuration