MCP Connectors Administration

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 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.

Some connectors need setup outside Unqork before an administrator can add them. Check 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 Administration > Environment Settings > Build Agent > MCP Connectors.

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.
(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.
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.
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.

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.

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.

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 (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 (ellipsis).
2. Select Delete. The Delete MCP Connector dialog opens and lists how many Creator sign-ins it removes.
3. Select Delete to confirm.

Deleting a connector cannot be undone.

You can also delete a connector from Manage Connection. In the dialog, select 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.