Connectors tab overview

The Connectors tab lets you authorize your personal third-party accounts with Mark (Optimizely Agent Platform). Mark administrators control which connectors and remote Model Context Protocols (MCPs) are available to the organization. Individual users then authenticate their personal accounts. Mark acts on their behalf using their permissions, data access, and identity.

To access the Connectors tab, click Connectors.

Mark administrators manage connector and remote MCP availability for the entire organization. The following connector types are available:

Both types display as tiles on the Connectors tab. After an administrator connects them, users can then connect to authenticate with the third-party provider.

Connector tools require configuration before users can authenticate with them. This is a one-time task per connector, and it applies to the whole organization.

To configure one, click Configure on its tile. If the connector is not installed yet, an Install modal displays first. After you install it, complete the Settings step, if the connector has one, and the Tools step. For the full procedure, see Configure a connector in the Connector tools overview.

After you configure it, the connector tile displays Connect on the Connectors tab for everyone in your organization to authenticate with their personal accounts.

To change a configuration later, click Configure on the tile again. Only administrators see this option.

As a Mark administrator, configure any of the following connectors for your organization:

To remove a connector tool, see Delete a tool registry. Removing a connector tool disables it for the entire organization. Users who have already authenticated with the tool lose access immediately, and the connector tile no longer displays on the Connectors tab.

Remote MCPs extend Mark's capabilities by connecting to external MCP servers that Optimizely has approved. Mark administrators connect to the remote MCP and then users can authenticate to view their own information.

As a Mark administrator, connect any of the following remote MCPs to make them available to your organization:

See Add a remote MCP provider for instructions. Connecting a remote MCP server extends Mark with tools and data from an external system.

Users cannot configure connectors. When a user clicks Contact Admin on a tile that is not configured yet, Mark sends a request to the administrators in your organization. The request displays in your Notifications, where you can go to the tile and configure the connector.

Mark administrators cannot view which users in their organization have authenticated a connector. Individual connections are private to each user.

Use the Connectors tab to link your personal third-party accounts to Mark. This ensures Mark uses your identity and permissions when calling connector tools, rather than a shared account.

You can connect, open, disconnect, and reconnect any connector that an administrator has already configured. You cannot configure a connector yourself. If a tile displays Contact Admin, the connector is not configured yet. Click Contact Admin to send a request to your Mark administrators, who receive it in their Notifications.

Authenticating your personal accounts provides the following advantages:

Before connecting to a third-party tool, ensure you meet the following requirements:

Authentication opens a pop-up window where you log in to the third-party service and grant Mark permission to access your account. This process uses OAuth, the standard authorization protocol for connecting to third-party services securely. The steps vary by connector.

After an administrator configures a connector, follow the steps for your connector to authenticate your personal account:

Manage your connections from the Connectors tab. Use the Active Status filter to display only connected items.

A connected tile displays Connected, along with the following actions:

Administrators also see Configure on a connected tile, which reopens the configuration dialog for the whole organization.

To reconnect, click Connect.

If you encounter issues when authenticating or managing a connector, see the following common scenarios and resolutions.

Mark opens a pop-up window to complete the authentication flow. If the window does not display after you click Connect, your browser may be blocking pop-ups.

Resolution – Check your browser's address bar for a blocked pop-up notification and click Allow. Then click Connect again.

If the window closes before you finish logging in or granting permissions, the connection does not complete and the connector status remains unchanged.

Resolution – Click Connect again and complete the steps in the Authenticate a connector section without closing the pop-up window manually. Ensure you click Allow or Authorize on the permissions page before you close the window.

After you complete the authentication steps, the connector status may not immediately display as Connected.

Resolution – Refresh the Connectors tab and check the status again. If the status still does not update, disconnect the connector and repeat the authentication steps.

OAuth tokens expire after a period of inactivity, a password change, or a revoked permission. When this happens, Mark can no longer act on your behalf until you re-authenticate.

Resolution – Locate the affected connector on the Connectors tab and click Refresh. Complete the login and permissions steps again to restore the connection.

The Connectors tab displays connectors Optimizely has added. If a connector you expect to see is not listed, a Mark administrator may not have configured it yet.

Resolution – Find the connector's tile and click Contact Admin. Mark sends a request to your administrators, who receive it in their Notifications.

An error state after completing authentication typically indicates a permissions mismatch, an unsupported account type, or an issue on the third-party service's end.

Resolution – Disconnect the connector, then reconnect and ensure you grant all requested permissions during the authorization step. If the error persists, verify that your third-party account has the required access level. For connector-specific guidance, see Authenticate a connector.

See the following documentation: