MCP connectors bring your other tools into Launchpad — Jira issues, Slack channels, Google Drive files, Monday.com boards, and more. You connect a tool once in App Hub, and Launchpad can work with it thereafter.
Beta — We're actively expanding MCP connectors. Share your feedback to help shape what's next.
Connectors use the Model Context Protocol (MCP), an open standard for connecting AI applications to external tools and data. Blueshift provides a set of ready-to-use connectors, and you can add any other MCP server as a custom connector.
MCP connectors and the Blueshift MCP Server
These are two separate features, and they work in opposite directions:
- MCP connectors — covered in this article — bring external tools into Blueshift for Launchpad to use.
- The Blueshift MCP Server works the other way. It lets external AI assistants, such as Claude or Codex, query your Blueshift account.
In this article
- Open MCP Connectors in App Hub
- Available connectors
- Set up a connector
- Adapter fields
- Add a custom MCP connector
- Use a connector in Launchpad
- Manage adapters
- Get help
MCP Connectors in App Hub
- Go to App Hub in the left navigation panel.
- Click MCP Connectors.
The page lists the connectors available on your account. Each card describes what you can do with that tool in Launchpad.
Available connectors
Blueshift provides the following connectors out of the box. The MCP server URL is filled in for you when you create the adapter. Change it only if your provider gives you a different endpoint, such as a region-specific or tenant-specific URL.
| Connector | MCP server URL | Provider documentation |
|---|---|---|
| Amplitude | https://mcp.amplitude.com/mcp |
Amplitude MCP Server |
| Atlassian | https://mcp.atlassian.com/v1/mcp/authv2 |
Atlassian Rovo MCP Server |
| BlueConic | Your own tenant URL, in the form https://<tenant>.blueconic.net/mcp
|
BlueConic Model Context Protocol (MCP) |
| Google Drive | https://drivemcp.googleapis.com/mcp/v1 |
Google Drive MCP reference |
| Monday.com | https://mcp.monday.com/mcp |
monday.com Platform MCP |
| Slack | https://mcp.slack.com/mcp |
Slack MCP server |
Check the provider's requirements first
Each provider decides what access you need before a connection succeeds. This can be an account on a supported plan, an integration your admin has to enable, or an OAuth application you register yourself. Review the provider documentation linked above before you create the adapter.
Set up a connector
The steps are the same for every connector. Each connection is saved as an adapter, and you can add more than one adapter for the same connector — for example, one per workspace or region.
- On the MCP Connectors page, click the connector you want to set up, then click Configure.
- Click + Adapter.
- Enter a name for the adapter, then complete the Authorization section. See Adapter fields below.
- Click Log in to MCP server and sign in to the provider in the browser. Until you do, the page shows that authorization is still required.
After the connection succeeds, the adapter is listed under Active Adapters, and you can start using it in Launchpad.
Adapter fields
| Field | Description |
|---|---|
| MCP Server URL (required) | The address of the MCP server. Filled in for the connectors listed above. Enter your own URL for BlueConic and for custom connectors. |
| Authentication Mode (required) | How Blueshift authenticates with the MCP server. OAuth 2.0 is selected by default and is recommended for secure access. |
| OAuth Client ID and OAuth Client Secret | Optional. Needed only when the provider requires you to register your own OAuth application. Leave both blank when the provider supports dynamic client registration. |
| OAuth Setup Mode | Leave as Auto-detect unless the provider tells you to configure the OAuth endpoints manually. |
| Use PKCE | Leave as Auto-detect unless the provider requires a specific setting. |
| Additional Headers | Optional. HTTP header key-value pairs sent with every request to the MCP server. Add these only when the provider asks for them. Click + Add More for another header. |
Registering the Blueshift redirect URL
If the provider asks for a redirect or callback URL when you create an OAuth application, use the URL for your region:
-
US:
https://app.getblueshift.com/api/v1/account_app_profiles/mcp_callback -
EU:
https://app.eu.getblueshift.com/api/v1/account_app_profiles/mcp_callback
Add a custom MCP connector
If the tool you need is not listed, add its MCP server as a custom connector.
- On the MCP Connectors page, click + Add MCP App.
- Upload a logo, name the app, and add a description. Your team sees this name and description on the connector card, so make them specific.
- Click Save.
The custom connector now appears alongside the others. Configure it and add an adapter the same way — see Set up a connector — using the MCP server URL.
Editing a custom app
Custom connectors show an Edit MCP App link on the configuration page, where you can change the logo, name, and description. Out-of-the-box connectors do not, because their app details are fixed. You can still add and edit adapters for them.
Use a connector in Launchpad
There is nothing extra to switch on. Once an adapter is connected, ask for what you need in Launchpad in plain language, and Launchpad picks the right tool for the request.
Manage adapters
To see all adapters for a connector, open it in App Hub > MCP Connectors and click Configure. Each row shows when the adapter was last updated and by whom.
- Set as default — Makes this the adapter used by default for the connector. Useful when you have more than one.
- Edit Adapter — Opens the adapter to update its URL, authentication, or headers.
- Clone — Copies the adapter so you can modify it for another use. Access credentials are copied as well.
- Archive — Makes the adapter inactive without deleting it. Archived adapters are moved to the Archived Adapters section, and you can restore the adapters using the Unarchive option.
- Delete — Permanently removes the adapter.
Archiving or deleting affects Launchpad
When you archive or delete an adapter, its tools are no longer available in Launchpad. Anything that relied on that connector stops working until another adapter is connected.
Get help
For problems with connector setup in Blueshift, contact Blueshift Support. For questions about what a specific MCP server supports, or the access it needs, see that provider's documentation in Available connectors.
Comments
0 comments