MCP Connectors

Connect external MCP servers to your workspace and give LLM steps access to external tools.

MCP Connectors let you connect external Model Context Protocol (MCP) servers to your AirOps workspace. Once connected, you can select these connectors as tools in LLM steps, allowing the model to call external tools during execution.

Looking for AirOps as an MCP server? MCP Connectors let you bring external MCP servers into AirOps. If you want to connect AirOps data to tools like Claude Desktop or Cursor, see the AirOps MCP Server docs instead.

Adding an MCP Connector

To add a new connector, navigate to Settings > MCP Connectors and click Add Connector.

Add MCP Connector form

Fill in the following fields:

Field	Description
Name	A display name for the connector (e.g. "GitHub MCP", "Linear MCP").
URL	The MCP server endpoint URL.
Auth Type	How AirOps authenticates with the server: Access Token or OAuth.

Access Token Authentication

1. Select Access Token as the auth type.

2. Enter the token provided by your MCP server.

3. Click Save. AirOps will test the connection before saving.

OAuth Authentication

1. Select OAuth as the auth type.

2. Click Authorize. You will be redirected to the MCP server's OAuth flow.

3. Complete the authorization and you will be returned to AirOps.

4. The connector is saved automatically after successful authorization.

Managing Connectors

The MCP Connectors settings page lists all connectors in your workspace along with their connection status.

MCP Connectors list

From this page you can:

• Edit a connector's name, URL, or credentials.

• Re-authenticate an OAuth connector if the token has expired.

• Delete a connector that is no longer needed.

• View connection status to confirm the server is reachable.

After adding or updating a connector, use it in an LLM step to verify it works end-to-end. See Using MCP Connectors in LLM Steps for details.

Security

• All connector credentials are encrypted at rest using AES 256-bit encryption.

• Credentials are scoped to the workspace that created them and are not accessible by other workspaces.

• OAuth tokens are stored securely and refreshed automatically when supported by the MCP server.

Troubleshooting

Issue	Resolution
Connection test fails on save	Verify the URL is correct and the MCP server is running. Check that any required auth credentials are valid.
OAuth redirect fails	Ensure your browser allows popups from AirOps. Try authorizing in an incognito window to rule out extension conflicts.
Connector shows "Disconnected"	The MCP server may be down or the credentials may have expired. Try re-authenticating or updating the access token.
Connector not appearing in LLM step	Make sure you have selected a compatible model. The MCP Connectors dropdown only appears when a supported model is chosen.