Integrations Setup

Overview

Kindo supports integrations using a combination of Nango for Auth and standardizing on the MCP protocol for agents to access those underlying systems. Most of the MCP servers today are built in house and are run by the customer as part of a self managed installation, but there's a growing number of official hosted MCPs that we can directly access without a customer needing to run the MCP server in their environment. This document outlines how to get Kindo setup with these integrations in a self managed installation.

Nango Setup

Connecting Your Nango Server With Your SMK Install

1. Setting environment variable values in Kindo

2. Setting environment variable values in Nango

1. Set the value of Callback URL to:

   ${NANGO_URL}/oauth/callback
   

2. Webhook setup: In order to receive and register new integration connections,

   1. Set the primary webhook URL in Nango. In the Nango dashboard, under the Environment Settings tab, scroll down to the Webhooks URLs section. Set the value of Primary URL to:

      ${API_BASE_URL}/webhook/nango
      

      where API_BASE_URL corresponds to the value of the environment variable that is set in the api service. Make sure that the Prod environment is selected.

   2. Toggle ON Auth: new connection webhoooks . All other toggles can be set to OFF.

Configuring New Integrations In Nango

Integrations can be configured as follows:

After logging into Nango, click Integrations → Configure New Integration → Select desired integration/auth method

NOTE: Some integrations may support multiple authentication methods, please see the chart below for supported auth methods for each integration:

OAUTH2 Integrations

To connect an OAUTH2 integration, you will first need create an OAUTH app from within the integration. Guides for creating OAUTH apps for each integration can be found in Nango’s docs. (Select the desired integration/auth method and search for OAUTH app creation guides. e.g. Jira docs). NOTE: The callback URL should be \<NANGO_URL\>/oauth/callback . After creating the integration, you can then configure the Client ID and Client Secret with the values provided by the integration provider. Required scopes for each integration are listed in the table above.

BASIC, API_KEY, and OAUTH2_CC Integrations

For BASIC and OAUTH2_CC, no modification to the integration configurations should be necessary as all required credentials are specified on creation of the connection in the Kindo platform.

If setting up webhooks for Linear or Jira, proceed to the next section. If not, you may skip to “Syncing Your Nango Integrations With Your SMK App”.

Setting Up Integration Webhooks

Integration Webhooks set up through this method are required for using Integration Event triggers in the product.

Direct Webhook URL triggers do not require this configuration, and can be used with any system that supports webhooks by simply following the in-app instructions.

Prerequisites

• To set up a webhook for an integration, you must first configure a new integration in Nango (see section above).

Linear

In Linear, go to Settings → API and select the OAUTH app created in the previous section. Then, click the three dots and select “Edit Application”. Enable the “Webhooks” toggle and enter \<API_SERVICE_URL\>/webhook/integration-connection/linear as the webhook URL where API_SERVICE_URL is the publicly exposed URL for the Kindo API Service. Select “Issues” under “Data change events” and copy the webhook signing secret before saving. In Nango, paste the freshly copied webhook secret into the “Webhook Secret” input and save the changes. NOTE: Any connections created via the Kindo UI before configuring the webhooks in linear will have to be reauthenticated (deleted and reconnected in the Kindo UI)

Jira

No additional setup is needed.

Syncing Your Nango Integrations With Your SMK App

• Prerequisites:

  • Access to the Hatchet dashboard

• Use when:

  • You need to sync the integrations that are registered in Nango with your SMK Kindo application

• Steps:

  1. In the Hatchet dashboard, go to the Activity \> Runs tab

  2. Click the Trigger Run button, which will open a pop-up

  3. In the pop-up, under Task or Workflow, click the Select Task or Workflow button

  4. Search for and select the workflow sync-all-integration-configs-workflow

  5. Click the Run Task button

• Checking that it worked:
  • In the Hatchet dashboard, you should see something like:

- In the Kindo app, open the settings modal and click on the `INTEGRATIONS` tab. Under `Available Integrations`, you should see the api providers that were configured in Nango.

# MCP Servers Setup

Connecting Your SMK App to MCP Servers

After syncing your Nango integrations with your SMK app (see previous section), the integration configs will appear in the IntegrationConfig table in your database.

To connect MCP servers, you need to manually update the mcpServerUrl field in the IntegrationConfig table for each integration:

1. Sync your Nango integrations using the Hatchet workflow (see "Syncing Your Nango Integrations With Your SMK App" above)
2. Verify the configs are in the database: Check that the integration configs now appear in the IntegrationConfig table
3. Update the mcpServerUrl field: For each integration you want to enable, set the mcpServerUrl to the URL where that MCP server is accessible
4. Update the supportsWebhooks field: For integrations that support webhooks (currently Jira and Linear), set the supportsWebhooks field to true if you want to enable trigger functionality for those integrations

Example URLs (adjust based on your deployment's namespace and service naming conventions):

• Slack: http://mcp-slack.mcp:80
• Jira: http://mcp-jira.mcp:80
• Linear: http://mcp-linear.mcp:80

Note: The exact URL format will depend on your Kubernetes namespace configuration and service naming conventions.