Scope

This document explains how to connect a client tenant on the Unique AI platform to the FactSet MCP server. It focuses on the operational process required on both sides and does not replicate FactSet’s own technical documentation.

Access to this MCP server requires existing Factset licenses or the purchase of Factset licenses via Unique AI. For more details, please contact your Customer Success Manager.

Commercial and contractual prerequisite

Access to the FactSet MCP server depends on the client’s existing contract with FactSet.

Before any technical work begins, the client must contact their FactSet representative to:

• Confirm that MCP access is included in their contract.

• Ensure the relevant APIs and entitlements are enabled.

• Validate that their users are eligible for API-based access.

If this step is not completed, provisioning on either side will fail regardless of configuration on the Unique AI platform.

Setting Up the Client (Unique AI Customer Success)

Once FactSet confirms eligibility, the process moves to provisioning.

User Provisioning

The Unique AI Customer Success (CS) team must:

• Collect the list of users to be provisioned (FactSet accounts).

• Complete the required Excel provisioning template: XLSXAI Partner Program - User Entitlement Request_Unique.xlsxExcel spreadsheetDownload

• Open an issue in FactSet’s issue tracker (liaise with Product or Engineering if needed) with:

  • Product: Partner Program – User Provisioning

• Upload the completed Excel file to the issue.

This step ensures that the relevant users are authorized under the Partner Program integration used by Unique AI.

No user will be able to authenticate through the MCP server unless they are provisioned through this process.

Redirect URI configuration

Customer Success must also ensure that the client’s tenant redirect URI is configured on the shared FactSet client.

This requires coordination with Product or Engineering on the Unique AI side to:

• Retrieve the tenant-specific redirect URI.

• Confirm that this URI is registered on the FactSet OAuth client.

If the redirect URI is not correctly configured, OAuth authentication will fail during the authorization flow.

MCP server configuration in Unique AI

After provisioning and redirect URI configuration are complete, the client’s MCP Admin can configure the server in the Unique AI platform.

Prerequisites for the MCP Admin:

• Must have an active FactSet account.

• Must be provisioned via the Partner Program (as described above).

Configuration steps

1. Log in to the Unique AI platform.

2. Navigate to the MCP Admin panel.

3. Add a new MCP server with URL https://mcp.factset.com/content/v1.

4. Select OAuth with Advanced Settings.

5. Set the Client ID to 85315453b47f492aa31c57895c2ba89d

When setting up the OAuth credentials, no client secret is needed.

This Client ID corresponds to the shared FactSet client registered under Unique Partner Program integration.

The MCP Admin must complete the OAuth login flow using their own FactSet credentials. Once authenticated, the platform will connect to FactSet and enumerate the available capabilities for that user.

Shared client model and security considerations

Unique AI uses a single shared OAuth client registered with FactSet.

All client tenants reuse this same Client ID. This is intentional and does not create data visibility or security issues.

Important clarifications:

• Each user authenticates with their own individual FactSet account.

• Authorization tokens are user-scoped.

• Data access is determined entirely by the user’s FactSet entitlements.

• There is no cross-tenant data exposure through the shared client.

The shared client acts purely as an OAuth authorization layer. It does not override user-level permissions or entitlements enforced by FactSet.

Summary of required sequence

1. Client confirms MCP/API access with their FactSet representative.

2. Unique AI Customer Success provisions users via the Partner Program issue process.

3. Customer Success ensures tenant redirect URI is registered on the FactSet client.

4. MCP Admin (provisioned FactSet user) adds a new MCP server in Unique AI with URL https://mcp.factset.com/content/v1

5. OAuth flow is completed using Client ID 85315453b47f492aa31c57895c2ba89d.

6. Capabilities are enumerated based on the authenticated user’s entitlements.
   

If any step is skipped, authentication or capability discovery will fail