Skip to content
These docs are a preview of Self-Managed Kindo 2026.11, an upcoming release.

Integrations Setup

Kindo supports integrations that give agents access to external systems through the MCP protocol. Most MCP servers are built in-house and run by the customer as part of a self-managed installation, though a growing number of official hosted MCPs can be accessed directly.

To turn integrations on and supply their OAuth app credentials, see Set up integrations.

The integrations below have their authentication method and setup notes on this page. For the full inventory of integrations and the tools each one exposes to an agent, see the Tool Catalog.

IntegrationAuth MethodNotes
Azure DevOpsBASIC
BoxOAUTH2
Cisco CatalystBASIC
Cisco FMCBASIC
Cofense TriageOAUTH2_CC
CrowdStrike FalconOAUTH2_CC
DatadogAPI_KEY
DropboxOAUTH2Requires file and account scopes
GitHubOAUTH2Scopes: repo, read:org, user
GitLabOAUTH2Scopes: api
Google DocsOAUTH2Requires documents and drive scopes
Google DriveOAUTH2Requires userinfo and drive scopes
Google SecOpsOAUTH2Configured per connection
GrafanaAPI_KEY
GraylogBASIC
JiraOAUTH2Requires Jira API and User Identity API scopes
LinearOAUTH2Scopes: admin, read, write
Microsoft Entra IDOAUTH2
Microsoft OneDriveOAUTH2Requires Files scopes
Microsoft Outlook CalendarOAUTH2Requires Microsoft Graph calendar and contacts scopes
Microsoft TeamsOAUTH2Requires Teams and Chat scopes
Neo4jBASIC
NVDAPI_KEY
SailPointOAUTH2_CC
SAP S/4HANABASICOData and RFC variants
ServiceNowOAUTH2_CC
SlackOAUTH2Requires channels, chat, and users scopes
SmartsheetOAUTH2Requires sheets, folders, and workspaces scopes
SourcegraphAPI_KEY
SplunkAPI_KEY
Sumo LogicBASIC
TenableAPI_KEY

For OAUTH2 integrations, create an OAuth app within the target integration, using the callback URL in Set up integrations. Then supply its Client ID and Client Secret as described in Set up integrations.

BASIC, API_KEY, and OAUTH2_CC Integrations

Section titled “BASIC, API_KEY, and OAUTH2_CC Integrations”

No modification to integration configurations is necessary — all required credentials are specified when creating the connection in the Kindo platform.

Use the links below to create an OAuth app or obtain credentials for each provider.

ProviderSetup Guide
BoxBox Developer Documentation — OAuth 2.0 Setup
DropboxDropbox App Console
GitHubCreating an OAuth App
GitLabOAuth Provider
Google DriveOAuth 2.0 Protocol
JiraJira REST API Authentication
LinearLinear OAuth 2.0 Authentication
Microsoft (OneDrive, Entra ID, Teams, Outlook)Microsoft Identity Platform — Register an App
SlackSlack API — Creating an App
ProviderSetup Guide
CrowdStrike FalconSee instructions below
ServiceNowConnect to ServiceNow
CrowdStrike Falcon — Client Credentials Setup

Docs: CrowdStrike OpenAPI

  1. Log into your CrowdStrike Falcon console.
  2. In the left sidebar, navigate to Support and Resources > API Clients and Keys.
  3. Create a new API client.
  4. Set the Base URL to match your CrowdStrike region (e.g., US-1, US-2, EU-1, or US-GOV-1).
  5. Click the client ID row to view and configure scopes. Grant the scopes required by your Kindo integration.
  6. Copy the Client ID and Client Secret — these are entered when creating the connection in the Kindo platform.
ProviderSetup Guide
GrafanaService Accounts
NVDRequest an API Key
TenableAuthorization
ProviderSetup Guide
Azure DevOpsPersonal Access Tokens
Sumo LogicAccess Keys

Integration webhooks are required for using Integration Event triggers. Direct Webhook URL triggers do not require this configuration.

  1. In Linear, go to Settings > API and select the OAuth app created earlier.

  2. Click the three dots > Edit Application.

  3. Enable the Webhooks toggle.

  4. Enter <API_SERVICE_URL>/webhook/integration-connection/linear as the webhook URL.

  5. Select Issues under “Data change events”.

  6. Copy the webhook signing secret.

  7. In Nango’s dashboard, paste it into the Linear integration’s Webhook Secret and save. To see the dashboard’s address, username and password, run kindo logins --show-secrets.

    Linear webhook configuration in the OAuth app settings

No additional setup is needed for Jira webhooks.

On a Self-Managed install, you choose which integrations are on, then apply the configuration. See Set up integrations.

Then confirm in the Kindo app under Command Center > Manage Your Integrations:

The Kindo integrations settings showing available API providers

Nothing to set up. Applying the configuration connects each integration you turn on to its MCP server. Integrations that support event webhooks (for example Jira and Linear) need the provider-side steps in Integration Webhooks.