Connect an MCP server

About

This guide adds an MCP server to Falcon AI as a connector. Successful discovery enables all returned tools, so review and narrow the allowed-tool selection before using the connector in chat. See MCP Connectors for what a connector is. You name it, point it at the server, choose how Falcon AI talks to it and signs in, then test the connection and discover its tools.

Before you start, make sure you have access to Workspace Settings in your workspace, the MCP server’s URL, and any credential the server requires, such as an API key or bearer token.

Open the Connectors page

Connectors live on the Falcon AI Connectors page, under Workspace Settings in Settings. Open Settings, then click Falcon AI Connectors in the sidebar to go straight there. Click Add Connector, top right, to open the form; on an empty page the Add your first connector button in the middle opens the same one.

Connectors are a workspace setting, so one you add here is available to everyone in the workspace, not just to you

Name it and point it at the server

Give the connector a Name and its Server URL, the address of the MCP server you’re connecting to. Both fields are required to save.

Choose the transport

Set Transport to how Falcon AI should talk to the server. Streamable HTTP is the normal choice for a current MCP server. Pick SSE (Legacy) instead if you’re connecting to an older server that still expects that transport.

Choose the authentication

Set Authentication to whatever the server expects. The form reveals the fields that method needs:

• None: skips authentication entirely
• API Key: adds Header Name and Header Value fields
• Bearer Token: adds a single Bearer Token field
• OAuth 2.0: no extra fields, you sign in after saving

Fill in whatever fields appear, then click Create to save the connector.

Sign in to an OAuth connector

If you set Authentication to OAuth 2.0, saving the connector doesn’t sign you in. Authentication happens as a separate step. Once saved, select the connector in the list on the left to open its detail pane, where you’ll find Re-authenticate. That’s the button for both your first sign-in and any later ones: click Re-authenticate, then approve access in the provider’s sign-in window. A successful callback closes the window and refreshes the connector details. Don’t wait for an Authentication updated. message in Settings: the OAuth popup flow does not display that success message. If sign-in fails, use any error shown by the provider or shown briefly in the callback window (it closes itself after a moment), confirm you approved access, and retry Re-authenticate.

OAuth sign-in and reauthentication can also trigger tool discovery, which enables every returned tool and replaces any previous allowed-tool selection.

Authentication can succeed even if tool discovery fails. A Connected chip is not proof of successful discovery, and an existing Discovered Tools list can remain from an earlier successful attempt. Run Discover Tools and check its result when you need to confirm that the list was refreshed.

Test the connection and discover its tools

With the connector saved and, for OAuth, signed in, select the new connector in the list on the left to open its detail pane. This is where Edit, Discover Tools, Test Connection, and Delete all live, plus Re-authenticate on a connector that signs in through OAuth. Click Test Connection to confirm Falcon AI can reach it. While it runs, the button reads Testing…. A successful test shows Connection test succeeded. unless the response supplies another message. A failed test shows available error details, falling back to Connection test failed. when none are available.

Once the connection is good, click Discover Tools (it reads Discovering… while it runs) to have the server report what it offers. A successful pass shows something like Discovered 4 tools. A failed one shows available error details, falling back to Tool discovery failed. when none are available.

Discovery stores what it found against the connector, so the list is still there when you come back without re-running it

If testing or discovery fails, use the reported error to guide troubleshooting rather than assuming the form is the cause. Check the Server URL, the server’s expected Transport, and the authentication settings. For API Key, check both Header Name and Header Value. If those settings are correct, investigate server availability, network access, or a platform error. Retry the failed action after addressing the reported problem.

Narrow down the tools

A successful discovery turns every tool it found on, so Falcon AI can already call all of them. The next step is cutting that set back to the ones you actually want, covered in Choose connector tools.

Edit or delete a connector

Select the connector in the list on the left to open its detail pane, then click Edit to change its name, URL, transport, or authentication, and click Save to save your changes.

When editing an API Key or Bearer Token connector, leave Header Value or Bearer Token blank to keep the stored secret. A blank field does not mean no secret is stored, and saving it blank does not clear the secret. Enter a new value only when you want to replace it.

Re-run Test Connection and Discover Tools after changing connection settings, then review your allowed-tool selection. Click Delete to remove a connector you no longer need.

Next Steps