Overview

This guide explains how to connect Claude to One Model using the Model Context Protocol (MCP).

Once connected, Claude can securely query governed workforce metrics from One Model and incorporate those results directly into conversational workflows such as analysis, document drafting, reporting, and presentations.

By connecting Claude to One Model via MCP, you can:

• Reduce context switching by querying workforce data directly from Claude
• Stay within your existing workflow while drafting content, writing code, or building presentations
• Combine AI reasoning with trusted One Model metrics to answer complex workforce questions

Please Note: One Model’s MCP integration is currently in an early-access phase. Because AI platforms update their interfaces frequently, you may find that some buttons, menu names, or configuration steps have shifted slightly since this guide was published.

• System Variations: Steps may vary depending on your specific tenant setup, regional settings, or administrative permissions.
• Help Us Improve: If a step looks different in your system or you encounter an unexpected result, please let us know! Use the Feedback Form to help us refine these instructions for the final release.

Terminology & Notes

• In Claude, MCP integrations are referred to as 'Connectors'. These connectors provide access to external systems such as One Model. 

Audience & Prerequisites

This guide is intended for:

• One Model Administrators responsible for setup, configuration and publishing
• Business Users and Analysts with approved access who will connect to and use the app

Part 1: One Model Administrators 

Setup, Configuration, and Publishing

To authorize the connection (the 'handshake') between Claude and your One Model production instance, an Administrator must have the appropriate access levels to both platforms.

Required Permissions in One Model

Ensure your user account is assigned an Application Access Role (AAR) with the following permissions enabled:

• CanAccessOneModelMCP - Allows use of the MCP to communicate with Claude or other external AI tools
• CanConfigureCompany - Grants access to high-level company settings

These permissions are configured via:  Admin > Application Access Role > [Select Role] > Permissions.

Integration Client Configuration

Once permissions are granted, Administrators manage authorized AI integrations through the Integrations page.  This ensures that only approved external tools can access data from your One Model instance.

Create a Client Integration in One Model 

• Log into your One Model production instance
• Navigate to Admin > Integration
• Click Create New and select Claude

Approved Client List

For security and compliance, One Model uses a Client Rule Approve List to control which external applications are allowed to connect. 

• You must specify approved client metadata (such as redirect/return URLs)
• This ensures that data is only shared with platforms vetted by your Security and Compliance teams

Pre-configured Templates:  One Model provides pre-configured connector templates for major AI providers. When selecting ChatGPT, Microsoft 365 Copilot, or Claude, required return URLs are auto-populated.

Custom Integrations: For proprietary or unsupported AI tools, select Custom and manually define required metadata fields and allowed values.

Creating the Claude Connector

Required Permissions in Claude

• Creating a custom connection in Claude requires a user who is in an “Owner” role.

Create a new Custom Connector

1. Open the Organization Settings page and then open the Connectors tab

2. Click the Add custom connector button near the bottom of the page below all of your existing connectors
3. To configure the connector enter:
   • Name:  Whatever you want the connector to be called in Claude, e.g. One Model
   • Remote MCP server URL: the endpoint for your One Model MCP server
     • Example: https://api.[companyid].onemodel.us/mcp
     • Be sure to use the correct URL for your environment (production)
   • OAuth Client ID: the One Model team will provide this to you (in the near future Admins will be able to generate this within the One Model app)
   • OAuth Client Secret: the One Model team will provide this to you (in the near future Admins will be able to generate this within the One Model app)
   • Click the Add button
   • If everything worked correctly you will now see your new connector in the list on this page.

Connecting the new Connector to One Model

1. Open the Settings page and then open the Connectors tab

2. Locate your new connector (it will appear grey’d out)
3. Click the Connect button
4. You should then receive a popup page to enter your login details:
   • Email address: this is the email address you use to log into your One Model instance
   • Password: For this early-access phase, this field serves as a placeholder. Please enter a temporary string e.g. ‘1234’ to proceed (just don’t leave it blank).
   • CompanyId: This is your One Model instance name. When looking at your One Model URL it is the prefix e.g. https://[companyid].onemodel.us/
   • Then press the Login button
   • NB: This login page has some redundant info for now, but that will be fixed in the near future.

Accept Permissions

5. A confirmation screen will display the connector’s capabilities
   • These permissions are defined by One Model
   • They are read-only during setup
6. Click Accept to finalize the connection.

Test the Connection

7. Start a new chat (if you click the + button you will be able to see all connectors currently active, which should include your new One Model connector

8. Enter a query that requires One Model data, such as:
   • What is my external hire rate trend?
   • What is my current headcount?

The query is routed through One Model’s MCP layer and returns a governed, data-driven response.

Tip: If you receive an error or no data, verify permissions, MCP URLs, and connector visibility.

Part 2: Business Users and Analysts

Connecting to and Using the One Model App 

Required Permissions

To connect Claude to One Model, your user account must have an Application Access Role (AAR) with:

• CanAccessOneModelMCP enabled

This is managed by your One Model Administrator via: Admin > Application Access Role > [Select Role] > Permissions

Log in to One Model

Log in (or use SSO) to your company’s One Model production instance.

Connecting the new Connector to One Model

1. Open the Settings page and then open the Connectors tab

2. Locate your new connector (it will appear grey’d out)
3. Click the Connect button
4. You should then receive a popup page to enter your login details:
   • Email address: this is the email address you use to log into your One Model instance
   • Password: enter anything into this field (just don’t leave it blank)
   • CompanyId: This is your One Model instance name. When looking at your One Model URL it is the prefix e.g. https://[companyid].onemodel.us/
   • Then press the Login button
   • NB: This login page has some redundant info for now, but that will be fixed in the near future.

Accept Permissions

5. A confirmation screen will display the connector’s capabilities
   • These permissions are defined by One Model
   • They are read-only during setup
6. Click Accept to finalize the connection.

Test the Connection

7. Start a new chat (if you click the + button you will be able to see all connectors currently active, which should include your new One Model connector

8. Enter a query that requires One Model data, such as:
   • What is my external hire rate trend?
   • What is my current headcount?

The query is routed through One Model’s MCP layer and returns a governed, data-driven response.

Tip: If you receive an error or no data, verify permissions, MCP URLs, and connector visibility.

Feedback Form

We encourage beta testers to complete the Feedback Form to share what’s working well, report issues, and suggest enhancements.

If you experienced app visibility or discoverability issues, please note:

• Whether the app was newly published or republished
• Whether Developer Mode was enabled at the time