LLMs.txt directory

Preparing an external app for an AgentSpot connector

Some applications require you to turn on MCP access and create credentials on their side before AgentSpot can connect to them. Use this page to prepare the application, collect the values AgentSpot asks for, and fix common setup problems.

Overview

AgentSpot connects to external applications through their remote Model Context Protocol (MCP) servers. For many connectors in the Available Connectors list, you only click Add and sign in. Other vendors require setup in their own admin console first.

Vendor-side setup usually includes one or more of the following:

  • Turning on MCP access, or setting up an MCP server, which gives you an MCP server URL

  • Creating an OAuth app, which gives you a Client ID and sometimes a Client Secret

  • Creating an access token, such as a personal access token or API token

  • Adding the AgentSpot callback URL to the app’s list of allowed redirect URLs

Vendors change their setup steps over time. If the steps on this page do not match what you see, follow the vendor’s current documentation.

Before you begin

  • You need the Can manage AgentSpot privilege. For details, see Managing users.

  • You need administrator access to the external application, or help from someone who has it.

  • Your company must have a license for the external application that includes MCP or API access.

Values to collect

Depending on the application, AgentSpot asks for some or all of the following values when you register the connector.

Value What it is Where to get it

Server URL

The address of the application’s MCP server.

Many connectors in the catalog already include it. For others, the URL is specific to your organization. Copy it from the vendor’s admin console or setup page.

Client ID

Identifies the OAuth app you created in the external application.

The vendor’s developer or admin console, after you create the app.

Client Secret

A private value paired with the Client ID.

Same place as the Client ID. Some vendors do not issue one.

Token

A static credential, such as a personal access token, used with bearer token authentication.

The vendor’s user or developer settings.

Callback URL (also called redirect URL)

The address the vendor sends users back to after they approve access.

Enter this value in the external application: https://oauth.thoughtspot.app/callback
Leave Client ID and Client Secret empty for connectors that support automatic registration. AgentSpot registers itself with the vendor when you connect.

General setup process

  1. In the external application: Turn on MCP access and note the MCP server URL, if the vendor provides one.

  2. In the external application: If the vendor requires an OAuth app, create one. Add https://oauth.thoughtspot.app/callback as a redirect URL, and note the Client ID and Client Secret.

  3. In AgentSpot: Go to 10 Admin Settings > Connectors and add the connector with the values you collected. For details, see Managing connectors.

  4. Connect your own account: From your user menu, select Connectors and click Connect on the new connector.

  5. Share the connector with your organization when it works. For details, see Sharing a connector with your organization.

Setup examples for common applications

The following examples cover applications that require vendor-side setup.

Salesforce

Salesforce requires you to expose an MCP server for your Salesforce org before AgentSpot can connect.

In Salesforce:

  1. Follow the Salesforce documentation for hosted MCP servers: Salesforce hosted MCP servers.

  2. When asked for a callback URL, enter https://oauth.thoughtspot.app/callback.

  3. Note the following values:

    • The MCP server URL. It depends on your org type. Production orgs and sandbox or scratch orgs each have their own endpoint.

    • The Consumer Key, which AgentSpot calls the Client ID.

In AgentSpot:

  1. Go to 10 Admin Settings > Connectors.

  2. Find Salesforce and click Add.

  3. For Server URL, enter the MCP server URL from Salesforce.

  4. For Client ID, enter the Consumer Key.

  5. Click Register Connector.

HubSpot

In HubSpot:

  1. Follow HubSpot’s instructions to create an MCP app: HubSpot MCP server.

  2. When asked for a Redirect URL, enter https://oauth.thoughtspot.app/callback.

  3. After you create the app, note the Client ID and Client Secret.

In AgentSpot:

  1. Go to 10 Admin Settings > Connectors.

  2. Search for HubSpot and click Add.

  3. For Authentication, select OAuth 2.1.

  4. Enter the Client ID and Client Secret from HubSpot.

  5. Click Register Connector.

Slack

The Slack connector lets agents read and act in Slack through the Slack MCP server. It is separate from the Slack bot, which lets users talk to agents from a Slack channel.

In Slack:

Slack requires a Slack app that hosts the MCP server. For details, see the Slack documentation: Slack MCP server.

  1. Go to api.slack.com/apps and click Create New App.

  2. Select From a manifest.

  3. Select the workspace to install the app in, then click Continue.

  4. Paste the manifest from the Slack documentation. It includes the scopes each MCP tool needs.

  5. Click Continue > Create and approve the installation for your workspace.

  6. In the app settings, open the Agents section and turn on Slack Model Context Protocol (MCP) Server.

  7. Go to OAuth & Permissions and review the scopes. Leave them as they are unless you want to limit what AgentSpot can do in Slack.

  8. Under Redirect URLs, click Add New Redirect URL, enter https://oauth.thoughtspot.app/callback, click Add, and then click Save URLs.

  9. Go to Basic Information > App Credentials and note the Client ID and Client Secret.

Any change to scopes or redirect URLs takes effect only after you reinstall the app. Go to Install App and reinstall it.

In AgentSpot:

  1. Go to 10 Admin Settings > Connectors.

  2. Search for Slack and click Add.

  3. Enter the Client ID and Client Secret from your Slack app.

  4. Click Register Connector.

  5. From your user menu, select Connectors, click Connect on Slack, and approve the permissions in Slack.

Troubleshooting

The connector does not appear in the Available Connectors list

Add it as a custom connector with the vendor’s MCP server URL. If the application does not have an MCP server, AgentSpot cannot connect to it. For details, see Custom connectors.

The vendor shows a redirect URL or callback error during sign-in

Make sure https://oauth.thoughtspot.app/callback is listed as an allowed redirect URL in the external application, with no extra characters or trailing spaces. Some vendors, such as Slack, also require you to reinstall the app after you change it.

The connection fails after you change scopes or permissions in the vendor app

Reinstall or republish the app in the vendor console, then connect again in AgentSpot.

The connector fails and the steps on this page look different

Check the vendor’s documentation to confirm your account is set up to accept MCP connections. Vendor setup steps change over time.

An agent cannot use a connector

Make sure that you have connected your own account (user menu > Connectors > Connect), and that the agent includes the connector (open the agent, click Edit Agent, and select the connector).

The connection stops working after some time

Connectors that use a static token, such as a personal access token, do not refresh automatically. When the token expires, create a new token and connect again.

Related information