> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Adding MCP Connectors

> Add a remote MCP server from the dashboard and choose when to link an account.

An MCP connector turns any remote MCP server into a StackOne [connector](/gateway/concepts/connectors). Its tools become [actions](/gateway/concepts/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](/connectors/introduction) 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](/secure/identity-and-access/roles-and-groups/project-roles) for what each role can do.

<Steps>
  <Step title="Configure a new MCP connector">
    1. In the StackOne dashboard sidebar, open [Connectors](https://app.stackone.com/connectors).
    2. Click **Add MCP Connector**.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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](/gateway/concepts/linked-accounts). 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.

    <Note>
      **Project Members** always link their account straight away. The connector and the account stay disabled until a **Project Admin** or **Organization Admin** enables them.
    </Note>
  </Step>

  <Step title="Create the connector">
    * With **Link Now**, click **Next**, then link the account in the StackOne Hub.
    * With **Link Later**, click **Save**.

    <Warning>
      Closing the StackOne Hub before the account is linked **removes the connector**. Run through these steps again to add it.
    </Warning>
  </Step>
</Steps>

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.

<Note>
  An MCP connector has no actions until an account is linked to it, so a connector saved with **Link Later** shows none at first.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Scoping Connectors" icon="sliders" href="/secure/scoping-connectors">
    Choose which actions and events a profile exposes.
  </Card>

  <Card title="AI Platforms" icon="robot" href="/connect/ai-platforms/overview">
    Connect the client your agents run in to StackOne.
  </Card>

  <Card title="Linking Accounts" icon="link" href="/connect/managing-connectors/linking-accounts">
    View, re-authenticate, and remove the accounts your agents act on.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.