--- title: "MCP Connectors Administration" slug: "mcp-connectors-administration" tags: ["administration", "unqorkai"] status: "new" updated: 2026-11-13T17:07:06Z published: 2026-11-13T17:07:06Z canonical: "docs.unqork.io/mcp-connectors-administration" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # MCP Connectors Administration > [!WARNING] > MCP Connectors is a Beta feature for environments with UnqorkAI. A connector sends the content it retrieves to the model the Build Agent runs on. Test each connector and verify the Build Agent's results before relying on them. The MCP Connectors administration page is where administrators add, share, and manage the connectors the [Build Agent](/unqorkai/docs/build-agent-overview) can use. A connector lets the Build Agent read from and write to one system outside Unqork, like Jira or Google Drive. For what connectors are, which systems are available, and how Creators sign in, see [MCP Connectors for the Build Agent](/unqorkai/docs/mcp-connectors-for-the-build-agent). Some connectors need setup outside Unqork before an administrator can add them. Check [Available Connectors](/unqorkai/docs/mcp-connectors-for-the-build-agent#available-connectors) first. Creators can open this page if their Creator role is not **Environment:BASIC**. To add a connector, a Creator's role must have the Create permission for Services. The page is available only when UnqorkAI is on for the environment. To open the MCP Connectors page, navigate to ![icon](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261113_170705_ca9f38d01f5243f4a4338e22a244314f.svg?sv=2026-02-06&spr=https&st=2026-11-14T00%3A06%3A42Z&se=2026-11-14T01%3A06%3A42Z&sr=c&sp=r&sig=8%2FMXX%2BcpbXNjCXH0WelaIBcaFoSGmmOcvk2Twk%2B8SB0%3D) **Administration** > ![icon](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261113_170705_a14cbdf4f6e34c5d808b73f971cf1c1b.svg?sv=2026-02-06&spr=https&st=2026-11-14T00%3A06%3A42Z&se=2026-11-14T01%3A06%3A42Z&sr=c&sp=r&sig=8%2FMXX%2BcpbXNjCXH0WelaIBcaFoSGmmOcvk2Twk%2B8SB0%3D) **Environment Settings** > ![icon](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261113_170705_a23a7ca2f91745b39577e2482561f427.svg?sv=2026-02-06&spr=https&st=2026-11-14T00%3A06%3A42Z&se=2026-11-14T01%3A06%3A42Z&sr=c&sp=r&sig=8%2FMXX%2BcpbXNjCXH0WelaIBcaFoSGmmOcvk2Twk%2B8SB0%3D) **Build Agent** > **MCP Connectors**. ![[docs-interactive-image:{"surface":"admin/mcp-connectors","anchors":{"Add Connector":"add-a-connector","Connector":"connector-list","Tools On":"connector-list","Access":"connector-list","Enabled":"connector-list"}}] MCP Connectors administration page with a search field, Add Connector, and a table of connectors with the Tools On, Access, and Enabled columns](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261113_170705_12b593b113a64e0a836ab55320d01ffe.png?sv=2026-02-06&spr=https&st=2026-11-14T00%3A06%3A42Z&se=2026-11-14T01%3A06%3A42Z&sr=c&sp=r&sig=8%2FMXX%2BcpbXNjCXH0WelaIBcaFoSGmmOcvk2Twk%2B8SB0%3D) ## Connector List The MCP Connectors page lists every connector in the environment. Selecting a row opens **Manage Connection** for that connector. | Element | Description | | --- | --- | | **Search Connectors** | Filters the list of connectors. | | **Add Connector** | Opens the **Add MCP Connector** dialog. The button is visible only to Creators whose role has the Create permission for Services. | | **Connector** | The connector's logo, title, and description. | | **Tools On** | How many tools the Build Agent can use, out of all the tools the system offers. For example, **3 of 9**. A badge marks tools the system added since the last review. | | **Access** | Who can use the connector. The column displays **Entire Environment** or a workspace count, like **2 Workspaces**. Hover over a workspace count to see the workspace names. | | **Enabled** | A switch that turns the connector on or off. When the switch is off, no Creator can use the connector. Its settings and each Creator's sign-in are kept. | | ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261113_170705_3056add8438043af819cd2d1d6ab4bb9.svg?sv=2026-02-06&spr=https&st=2026-11-14T00%3A06%3A42Z&se=2026-11-14T01%3A06%3A42Z&sr=c&sp=r&sig=8%2FMXX%2BcpbXNjCXH0WelaIBcaFoSGmmOcvk2Twk%2B8SB0%3D) (**ellipsis**) | Opens a menu with **Manage Connection** and **Delete**. | When the environment has no connectors, the page displays **No Connections to Display**. ## Add a Connector The **Add MCP Connector** dialog has three steps. The current step displays below the dialog title, like **Step 1 of 3: Choose a Connector**. To add a connector: 1. At the top right of the page, select **Add Connector**. 2. In **Step 1 of 3: Choose a Connector**, find the connector's card. On that card, select **Add Connector**. If the environment already has that connector, the button reads **Add Another Connector**. 3. In **Step 2 of 3: Connector Details**, enter the connector's settings. See [Connector Details](/unqorkai/docs/mcp-connectors-administration#connector-details). 4. Select **Create Connector**. The dialog moves to **Step 3 of 3: Select Tools**. 5. Choose the tools the Build Agent can use. See [Choose Tools](/unqorkai/docs/mcp-connectors-administration#choose-tools). 6. Select **Save Tools**. To choose tools another time, select **Finish Later**. The page then displays a message like **Exa added with 2 tools on.** For an OAuth connector, the message also explains how to connect to a second site from the same company. ### Connector Details Step 2 holds the settings for one connector. The **Authorization** section changes based on the connector's sign-in type. | Setting | Description | | --- | --- | | **Name** | The connector's unique name. Required. The name is permanent. It cannot change after the connector is created. | | **Title** | The name Creators see in the Build Agent. Required. | | **Description** | A short summary of what the connector reaches. Required. | | **API key** | The shared key for an API key connector, like Exa or Firecrawl. Required for API key connectors. Every Creator who can use the connector shares this key. | | **OAuth client ID** and **OAuth client secret** | The OAuth client from the other company's console. Required for Google Docs and Google Drive. For Atlassian, the fields are optional. Select **Enter an OAuth Client Manually** to display them. | | **Share To** | Who can use the connector. Select **Environment** for every workspace, or **Workspaces** to pick specific workspaces. | > [!WARNING] > Treat an API key and an OAuth client secret like a password. Paste them only into the Unqork fields that ask for them. Do not put them in screenshots, tickets, chat messages, or shared documents. For OAuth connectors, the **Authorization** section displays a redirect URI. A redirect URI is the web address where the other system sends a Creator after they sign in. Google Docs and Google Drive need this address in their setup. See [Set Up Google Drive and Google Docs Connectors](/unqorkai/docs/set-up-google-drive-and-google-docs-connectors). The dialog also reminds administrators that content the connector retrieves is sent to the Build Agent's model. ### Choose Tools Step 3 lists the connector's tools under **Tool Inventory**. Each row has the tool's name and description, a classification drop-down, and a switch. Turn on the switch for each tool the Build Agent can use. A tool that is off never reaches the Build Agent. The first time Unqork finds a connector's tools, it turns on a tested set of default tools. Tools the system adds later are marked **New** and are off until an administrator turns them on. The **Changed** badge marks a tool whose details changed. The **No longer offered** badge marks a tool the system removed. For OAuth connectors, the tool list is empty until the administrator connects their own account. Select **Connect** and sign in to see the tools. The classification drop-down sets whether the Build Agent treats a tool as a read tool or a write tool. Options include **Default**, **Read**, and **Write**. - **Default**: Uses the label the other system gives the tool. If that label does not say the tool only reads, the Build Agent treats it as a write tool. - **Read**: The tool only looks up information. - **Write**: The tool can change information in the other system. Unqork locks some tools as **Write**. Their drop-down is unavailable. For why classification matters to Creators, see [Read and Write Tools](/unqorkai/docs/mcp-connectors-for-the-build-agent#read-and-write-tools). ### Add the Same Connector Again An administrator can add the same connector more than once. Each copy has its own name, tools, and **Share To** setting. For OAuth connectors, each copy links to one site at that company. To connect to a second Atlassian site, for example, add Atlassian again. When a new copy reuses a name another connector already has, the dialog asks for a different name. Give the copy a distinct name, then pick the other site when the company asks. ## Manage a Connector To open a connector's settings, select its row. Or select ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261113_170705_3056add8438043af819cd2d1d6ab4bb9.svg?sv=2026-02-06&spr=https&st=2026-11-14T00%3A06%3A42Z&se=2026-11-14T01%3A06%3A42Z&sr=c&sp=r&sig=8%2FMXX%2BcpbXNjCXH0WelaIBcaFoSGmmOcvk2Twk%2B8SB0%3D) (**ellipsis**) on the row, then select **Manage Connection**. A dialog opens. Its sections include: - **Tools**: The same tool list as step 3. The section is collapsed by default. Select **Refresh Tools** to check the system for new or changed tools. - **Connections**: The **Connected Creators** table, with each Creator's name, email, and status. A **Needs attention** status means the Creator must connect again. - **MCP Connector Info**: The connector's details. It includes the **Definition** that Unqork sets, like the endpoint and sign-in type. The definition is read-only. Select **Save Connector** to save changes. The page displays **Connector saved.** A Creator whose role does not have the Update permission for Services can open the dialog but cannot change anything. ## Delete a Connector Deleting a connector removes its settings and every Creator's connection. Creators must connect again if an administrator adds the connector back. To turn off a connector for a while, use the **Enabled** switch instead. To delete a connector: 1. On the connector's row, select ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261113_170705_3056add8438043af819cd2d1d6ab4bb9.svg?sv=2026-02-06&spr=https&st=2026-11-14T00%3A06%3A42Z&se=2026-11-14T01%3A06%3A42Z&sr=c&sp=r&sig=8%2FMXX%2BcpbXNjCXH0WelaIBcaFoSGmmOcvk2Twk%2B8SB0%3D) (**ellipsis**). 2. Select **Delete**. The **Delete MCP Connector** dialog opens and lists how many Creator sign-ins it removes. 3. Select **Delete** to confirm. > [!CAUTION] > Deleting a connector cannot be undone. You can also delete a connector from **Manage Connection**. In the dialog, select ![Trash2](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261113_170706_2046e1ff4810486a936372f599c73b60.svg?sv=2026-02-06&spr=https&st=2026-11-14T00%3A06%3A42Z&se=2026-11-14T01%3A06%3A42Z&sr=c&sp=r&sig=8%2FMXX%2BcpbXNjCXH0WelaIBcaFoSGmmOcvk2Twk%2B8SB0%3D) **Delete Connector**, then confirm. The **Delete** option and the **Delete Connector** button are available only to Creators whose role has the Delete permission for Services. --- **Changelog** | Date | Change | | --- | --- | | 2026-11-06 | Renamed the article to MCP Connectors Administration. Moved Key Terms, Prerequisites, How Creators Sign In, and What Creators See to MCP Connectors for the Build Agent. | | 2026-11-06 | Created the article from source. | A functionality of a software. For example, Copy and Paste is a feature of a computer's operating system. Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. OAuth, or Open Authorization, is an authorization protocol that lets users grant third-party access to their information without sharing their passwords. OAuth is an industry standard that's used by many companies, including Google, Amazon, and Microsoft. APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. A key-value pair is a fundamental data structure where a unique "key" is associated with a specific "value," used for organizing and retrieving data efficiently, like in dictionaries or databases. Authentication secrets are a value of confidential information. For example, a password, security token, or cryptographic key, that is used to verify a user's identity during the authentication process to grant access to a system or application. URI (Uniform Resource Identifier) identifies a resource by name, location, or both. An API endpoint is the location where an API receives requests for a specific resource on its server. It's the point of contact between an API client and an API server, and is usually a uniform resource locator (URL) that provides the location of the resource. Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.