MCP Connectors

Connect external MCP servers to Falcon AI to use tools from services like Linear, Slack, GitHub, Sentry, and custom APIs.

About

Falcon AI comes with built-in tools for the Future AGI platform, but many workflows involve external services: project trackers, communication tools, monitoring systems, and internal APIs. MCP Connectors extend Falcon AI by connecting it to any server that implements the Model Context Protocol. Once connected, Falcon AI discovers the server’s tools and can call them during conversations alongside built-in platform tools.

This means tasks like “create a Linear ticket for this failing evaluation” or “post this cost report to Slack” happen inside Falcon AI without switching tools.


Examples

  • Project management: Connect Linear, Jira, or Asana to create and update issues from evaluation or trace analysis.
  • Communication: Connect Slack or email to share reports and alerts directly.
  • Monitoring: Connect Sentry or PagerDuty to pull error context into debugging conversations.
  • Internal APIs: Connect custom MCP servers that expose your organization’s tools.

Adding a connector

Open connector settings

Open Falcon AI settings and go to the Connectors section. Click Add Connector.

Add connector form

Configure the connection

Fill in the connector fields:

FieldRequiredDescription
NameYesDisplay name for the connector (e.g., “Linear”, “Sentry”)
Server URLYesThe MCP server endpoint URL
TransportYesstreamable_http (default, recommended) or sse (Server-Sent Events)
Auth typeYesHow to authenticate with the server (see below)

Configure authentication

Choose the authentication method that your MCP server requires:

Auth typeFieldsDescription
NoneNo authentication required
API KeyHeader name, Header valueSends a custom header with each request (e.g., X-API-Key: your-key)
Bearer TokenTokenSends Authorization: Bearer <token> with each request
OAuth 2.1Client ID, Client secret, Auth URL, Token URL, ScopesFull OAuth flow with automatic token refresh

Tip

For OAuth connectors, Falcon AI handles the entire authorization flow. After saving the connector, click Authenticate to open the OAuth consent screen. Tokens are stored securely and refreshed automatically when they expire.

Test the connection

Click Test Connection to verify that Falcon AI can reach the MCP server and authenticate successfully. If the test fails, the error message is displayed so you can debug the configuration.

Discover tools

Click Discover Tools to query the MCP server for its available tools. Falcon AI reads the server’s tool schema and displays the list with names, descriptions, and parameter definitions.

The discovery result is cached. Re-run discovery if the server adds new tools.

Enable tools

Not all discovered tools need to be active. Select which tools Falcon AI should have access to from the discovered list. Only enabled tools appear in conversations.

This is useful when a server exposes many tools but you only need a subset, keeping Falcon AI’s tool set focused and reducing context window usage.


Using connector tools in chat

Once enabled, connector tools appear in Falcon AI conversations alongside built-in platform tools. Falcon AI decides when to use them based on your request. Tool names from connectors are prefixed with the connector name to avoid collisions (e.g., linear_create_issue).

Examples:

“Create a Linear ticket for the faithfulness regression we found in the last evaluation run.”

“Post a summary of today’s error spikes to the #ml-alerts Slack channel.”

“Check Sentry for any new issues related to the summarization service.”


Transport options

MCP Connectors support two transport protocols:

TransportHow it worksWhen to use
Streamable HTTPStandard HTTP POST requests with JSON-RPC 2.0 payloadsDefault. Works with most MCP servers.
SSE (Server-Sent Events)Long-lived HTTP connection with server-pushed eventsUse when the server requires SSE transport or for streaming tool results.

Falcon AI automatically tries multiple endpoint paths (with and without /mcp suffix) to find the correct one for your server.


Managing connectors

  • Edit: Update any connector field from the Connectors settings page. Re-test and re-discover after changes.
  • Delete: Remove a connector and all its cached tool schemas. Tools from deleted connectors are immediately unavailable in conversations.
  • Re-authenticate: For OAuth connectors, click Authenticate again if the authorization has been revoked or if scopes need to change.

Next Steps

Was this page helpful?

Questions & Discussion