Connecting Claude to One Model via MCP

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
• CanRegisterMCPClients - Controls whether the user can manage pre-registration credentials for MCP clients. 
• CanConfigureCompany - Grants access to high-level company settings

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

Choose your Client Registration Path 

There are two ways to register Claude as an MCP client in One Model. Both result in a working connection - the difference is who controls the client credentials and how the connection is approved. 

Path 1 — Register a Dedicated MCP Client (recommended) 

• You generate dedicated OAuth credentials in One Model and paste them into Claude. You stay in control of credentials and can revoke them independently. 

Path 2 — Automatic Client Registration

• The OAuth Client ID and Client Secret are generated by the One Model team and provided to you to paste into Claude. Because the credentials originate outside your environment, this path offers less control than Path 1 - we recommend Path 1 wherever it's available to you. 

Path 1 - Register a Dedicated MCP Client (recommended)

This path generates a dedicated OAuth Client ID and Client Secret that you paste into Claude's custom connector configuration. Use this approach when you want to control the credentials yourself rather than relying on dynamic registration. 

Register the client in One Model

• Log into your One Model production instance
• Navigate to Admin > Integration
• Open the MCP Clients tab and click Register New Client

Complete the registration form:

• Client Name: A descriptive label that identifies this client in audit logs and the MCP Clients list, e.g. Claude Production
• Redirect URL: e.g. https://claude.ai/api/mcp/auth_callback 

Click Register

Capture your credentials

Once the client is registered, One Model will display the OAuth Client ID and OAuth Client Secret.

Important: Copy both values to a secure location before navigating away from the page. If you lose the secret, you'll need to register a new client.

You'll paste these values into the Claude connector configuration in the next section.

Next step: You've completed Path 1. Skip Path 2 below and go straight to Creating the Claude Connector. 
 

Path 2 - Automatic Client Registration 

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.

Next step: You've completed Path 2. Continue to Creating the Claude Connector. 

Creating the Claude Connector

Once you've completed your chosen registration path in One Model (Path 1 or Path 2 above), the next step is to create the matching connector in Claude. The steps are the same for both paths - only the OAuth Client ID and OAuth Client Secret fields are filled in differently. 

Required Permissions in Claude

Creating a custom connector in Claude requires a user with the Owner role on the Claude organization. 

Create a new Custom Connector

In Claude, open the Organization Settings page and then open the Connectors tab

Click Add in the top-right of the page and select Custom Web connector 

Configure the connector 

• Name:  A label for the connector as it will appear in Claude, e.g.  One Model
• Remote MCP server URL: Your One Model MCP server endpoint, formed by adding api. before your company ID and /mcp at the end of your One Model site URL. 
  • Format: https://api.[companyid].onemodel.[domain]/mcp
  • Example: https://api.acmecorp.onemodel.us/mcp
  • Supported domains: onemodel.us, onemodel.com.au, onemodel.ca, onemodel.eu
  • Use the URL for your Production environment 
• Fill in the OAuth Client ID and OAuth Client Secret fields based on the path you followed: 

Click Add 

If the connector was created successfully it will now appear in the list on the Connectors page. 

Verify the connection

Once the connector is created, you'll need to authorize it for your own session before you can test it. Follow the steps in Part 2: Business Users and Analysts to connect, accept permissions, and verify the integration is working.  

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

Open the Settings page and then open the Connectors tab

Locate your new connector (it will appear grey’d out)

Click the Connect button

Your login screen will look slightly different depending on whether your organization uses Single Sign-On (SSO):

• If you see a "Single Sign-On" click the button.
• Otherwise, enter your One Model email and password directly.

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 your password
• 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

Accept Permissions

A confirmation screen will display the connector’s capabilities

• These permissions are defined by One Model
• They are read-only during setup

Click Accept to finalize the connection.

Test the Connection

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

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