Skip to main content
An MCP connector turns any remote MCP server into a StackOne connector. Its tools become actions, and you govern it the same way as every other connector. Use one when the system your agents need already has an MCP server, such as one your team runs or one a provider publishes, and no pre-built connector covers it. If MCP connectors are enabled for your organization, Organization Admins, Project Admins, and Project Members can connect remote MCP servers directly from the dashboard. See Project Roles for what each role can do.
1

Configure a new MCP connector

  1. In the StackOne dashboard sidebar, open Connectors.
  2. Click Add MCP Connector.
2

Enter the server details

Set the following:
  • Name: what to call the connector in the connectors list. The connector’s key is derived from it and can’t be changed later.
  • Remote MCP Server URL: the public https:// address where the server accepts MCP requests.
  • OAuth Client ID and OAuth Client Secret, under Advanced Settings: only needed when the server signs in through OAuth and doesn’t register clients dynamically. Leave the secret empty for a public client that uses PKCE.
3

Account linking

Organization Admins and Project Admins choose one of:
  • Link Now: link an account in the StackOne Hub straight away to create a linked account. Its tools load as soon as the account is linked.
  • Link Later: save the connector without an account. Project Admins and Project Members can link one from the connector’s page, and its tools load once they do.
Project Members always link their account straight away. The connector and the account stay disabled until a Project Admin or Organization Admin enables them.
4

Create the connector

  • With Link Now, click Next, then link the account in the StackOne Hub.
  • With Link Later, click Save.
Closing the StackOne Hub before the account is linked removes the connector. Run through these steps again to add it.
For Organization Admins and Project Admins, the connector is available once the account is linked. Each tool on the server appears as an action on the Actions tab.
An MCP connector has no actions until an account is linked to it, so a connector saved with Link Later shows none at first.

​
Refresh actions

When the MCP server adds, changes, or removes tools, refresh the connector to pick them up. Refreshing needs at least one Linked Account on the connector that you have permission to use. StackOne asks the MCP server for its tools through the linked accounts and merges them into the connector:
  • New actions are added to the latest version when existing actions are unchanged.
  • A new connector version is created when actions are changed or removed. Connector Profiles that follow the latest version move to it, while profiles pinned to an earlier version stay on that version.
  • If a linked account can’t be reached, no actions are removed, because its tools may still exist.
1

Open the connector

  1. In the StackOne dashboard sidebar, open Connectors.
  2. Select the MCP connector.
2

Refresh actions

On the Library card, open the actions menu (⋯) and select Refresh Actions.

​
Delete an MCP connector

Only Organization Admins and Project Admins can delete an MCP connector from a project. Deleting an MCP connector permanently removes the connector and its Connector Profiles from the project. Any Linked Accounts on those profiles are archived and their credentials removed.
1

Open the connector

  1. In the StackOne dashboard sidebar, open Connectors.
  2. Select the MCP connector.
2

Delete the connector

  1. On the Library card, open the actions menu (⋯) and select Delete Custom Connector.
  2. Enter the connector name to confirm, then click Delete.
  3. If Connector Profiles or Linked Accounts depend on the connector, click Delete all to confirm the cascading deletion.

​
Next steps

Scoping Connectors

Choose which actions and events a profile exposes.

AI Platforms

Connect the client your agents run in to StackOne.

Linking Accounts

View, re-authenticate, and remove the accounts your agents act on.