MCP Servers

MCP (Model Context Protocol) servers allow you to expose AireGlu endpoints as tools and resources that MCP-compatible clients such as Claude.ai, Claude Desktop, Cursor, and other AI-powered applications can discover and invoke.

Tenant Access

MCP server features are enabled per-tenant. If you don't see AI Tools > MCP Servers in the navigation, contact support to request access for your tenant.

Key Concepts

• MCP Server - A named configuration containing one or more versions, each exposing a set of endpoints as tools and resources.
• Version - A semantic version (e.g. 1.0.0) within a server. Each version defines its own set of exposed endpoints and can be activated or deactivated independently.
• Default Version - The version used when an MCP client connects without specifying a version in the URI. Can be set during creation or changed later via the server actions menu.
• Tool - An endpoint exposed as an invocable action. MCP clients call tools to perform operations (e.g. submit data, trigger a workflow).
• Resource - An endpoint exposed as readable data. MCP clients read resources to retrieve information (e.g. fetch a dataset, read configuration).
• Connection URI - The URL an MCP client uses to connect to your server.

Permissions

MCP usage requires the following claims on your user account:

Action	Required Claim
View server list	list:McpServerConfig
View server details	view:McpServerConfig
Create a server	create:McpServerConfig
Edit a server	edit:McpServerConfig
Delete a server	delete:McpServerConfig
Connect a client to a server	run:Mcp

The first five claims cover server management in the AireGlu UI. run:Mcp is required to authenticate an MCP client (e.g. Claude.ai, Cursor) against a server - without it the client will complete OAuth login but every tool or resource call will fail.

Contact your administrator if you do not have the required permissions.

Navigation

MCP Servers are found under AI Tools > MCP Servers in the main navigation.