Clarier MCP connector

Overview

The Clarier MCP connector is a secure bridge between Claude and your organization’s Clarier workspace. It lets Claude use Clarier’s governed records as the source of truth for AI tools, vendors, requests, approvals, usage, and compliance.

The connector is hosted and maintained by Clarier. It uses the Model Context Protocol’s Streamable HTTP transport and OAuth 2.1 authentication, so users sign in with their existing Clarier account instead of copying API keys into Claude.

Tool availability is dynamic. A company administrator may enable or disable the connector, write actions, AI usage, identity, vendor timeline, or other features. Administrators also see capabilities that standard users do not.

At a glance

Before you connect

• An active Clarier account and membership in the company you want to connect.
• Access to Claude and permission to install or connect directory connectors in your Claude organization.
• The Clarier connector must be enabled for your company by a Clarier administrator.
• If your company requires Microsoft SSO, sign in to Clarier with Microsoft before connecting.
• Write actions appear only when your company enables them and you grant write access during connection.

Connect in Claude

1. In Claude, open Settings → Connectors or browse the Claude Connectors Directory.
2. Find Clarier and select Add or Connect.
3. A Clarier authorization page opens. Sign in with your existing Clarier account.
4. Choose the Clarier company you want this connection to use.
5. Review the requested access. Enable write access only if you want Claude to prepare and submit supported changes.
6. Approve the connection and return to Claude.
7. In a conversation, open Search and tools and make sure the Clarier tools you want to use are enabled.

Check that it works

If Clarier is not visible in your organization’s directory yet, contact your Clarier administrator or dev@clarier.ai. Pilot organizations may receive separate connection instructions from Clarier.

What you can do

Permissions and tool availability

Clarier does not expose the same tool list to everyone. Claude receives a tool catalog for the connected user’s current role and the company’s enabled features. The complete administrative read/write connection currently exposes up to 25 tools.

• A missing capability usually means it is not enabled for your company, role, or connection; it is not necessarily an error.
• The company selected during authorization is fixed to that connection. A prompt cannot switch the connector into another company.
• Clarier rechecks membership, role, SSO policy, feature availability, and connection status on every request.

Safe write actions

Supported writes use a prepare → review → commit flow.

1. Claude reads your company’s current request-form configuration and available choices.
2. Claude prepares the action without changing the Clarier record.
3. Claude shows every field that will be submitted, including defaults and optional fields that were left blank.
4. You can ask Claude to change any value and prepare it again.
5. Only after you explicitly approve the final field set does Claude commit the action.

Supported writes

• Create a new AI tool request — available to standard users and administrators when write access is enabled.
• Update an existing tool’s owner, category, or notes — administrators only, when write access is enabled.

Not supported through the connector

• Changing approval status.
• Approving or rejecting an approval request.
• Generating a new vendor report.
• Sending a request into an approval workflow.
• Uploading arbitrary files or Claude Skill packages.

Example prompts

For any write, explicitly ask Claude to show the complete proposed field set before it commits the action.

Tool reference

Technical tool names are shown for administrators and reviewers. Most users can simply describe the outcome they want in natural language.

Read tools available to eligible users

Administrator read tools

Write tools

Tools may be hidden when the connected role, company configuration, feature flags, or read/write consent do not permit them.

Security and data handling

Authentication and authorization

• Users authenticate through OAuth 2.1 with their existing Clarier account; no Clarier API key is entered into Claude.
• Each connection is bound to the specific Clarier company selected during authorization.
• Every request rechecks the connection, company membership, current role, SSO policy, and company feature settings.
• Companies can enable the connector as read-only or allow supported writes.
• Users can revoke their own connection from Clarier, and access stops immediately on subsequent connector requests.

Tenant and role isolation

• Claude cannot select a company by placing a company identifier in a prompt or tool argument.
• Record lookups are scoped to the connected company.
• Administrator-only information and actions are not exposed to standard users.
• If a user’s membership or role is removed, existing connector access is denied.

Data sent to Claude

When you ask Claude to use Clarier, the requested Clarier tool result is returned to Claude and becomes part of that conversation’s context. Anthropic’s handling of that content is governed by your Claude plan, organization settings, and agreement with Anthropic.

The Clarier connector does not read your unrelated Claude conversations, Claude memory, or conversation history. It does not use your customer data to train models.

Clarier does not persist raw read-tool prompts or results for the connector. Connection records, rate-limit metadata, security/audit events, and the allowlisted fields of a prepared write are retained as needed to operate and audit the service.

• Privacy policy
• Clarier trust information
• Service status

Manage or revoke a connection

Disconnect in Claude

Open Claude Settings → Connectors, select Clarier, and choose Disconnect. This removes Claude’s active connection.

Revoke in Clarier

In Clarier, open your user menu and select Connected AI clients. Revoke the Claude connection you no longer want to authorize.

Switch companies

Each active Claude connection is bound to one Clarier company. To use a different company, revoke or disconnect the existing connection and connect again, choosing the other company during authorization.

Troubleshooting

Clarier does not appear in Claude

Your Claude organization may not have installed or allowed the connector yet. Ask your Claude organization administrator to add Clarier, or contact dev@clarier.ai.

Authorization fails or the sign-in window does not open

Disconnect the Clarier connector in Claude, sign in to Clarier in a normal browser tab, and try Connect again. Confirm that pop-ups are allowed and that you are using the Clarier account invited to the intended company.

Microsoft SSO is required

Sign out of Clarier, sign back in using Microsoft, then reconnect the connector. Companies that enforce Microsoft SSO cannot authorize the connector from a non-SSO session.

The connector shows no tools

The connection may be disconnected or revoked, or the Clarier connector may be disabled for your company. Reconnect once. If tools are still missing, ask your Clarier administrator or contact dev@clarier.ai.

A tool or report is missing

Capabilities vary by role and company features. A vendor report must already exist in Clarier before the connector can read it. Generate or manage missing reports in the Clarier application.

Write tools are missing

Your connection may be read-only, your company may have disabled connector writes, or the action may require a company-administrator role. Reconnect and grant write access only if your administrator allows it.

A request is missing required information

Ask Claude to read the Clarier request-form options first. Your company controls which fields are enabled, required, and limited to specific choices.

The connector became unauthorized after working previously

The connection may have been revoked, your company membership or role may have changed, or the connector may have been disabled. Disconnect and reconnect only if you still have valid Clarier access.

The daily request limit was reached

Clarier applies a company-configurable daily connector limit. Try again after the next UTC day or contact your Clarier administrator.

I still need help

Email dev@clarier.ai with your company name, the approximate time of the problem, the Claude product you were using, and the visible error message. Never email access tokens, OAuth secrets, passwords, or confidential prompt content.

FAQ

What is MCP?

The Model Context Protocol is an open standard that lets AI clients discover and call tools provided by external services. Clarier uses MCP to make its governed AI records and supported actions available to Claude.

Does Claude receive everything in our Clarier workspace?

No. The connector returns only the information requested through an available tool, within the connected user's company and permissions. Tool outputs may still contain sensitive company information, so use them only in Claude environments approved by your organization.

Does the connector use a Clarier API key?

No. Users authenticate with OAuth 2.1 and their existing Clarier account.

Can a prompt switch the connector to another company?

No. The selected company is fixed to the authorized connection. Switching companies requires reconnecting and choosing the other company.

Can Claude approve or reject requests for me?

Not in the current connector. Claude can show approval items waiting for you and explain request progress, but approval decisions are completed in Clarier.

Can Claude submit a new AI tool request?

Yes, when your company and connection allow writes. Claude first prepares the full request for your review and submits it only after your explicit approval.

Why do different users see different tools?

The available tool list reflects the connected user's Clarier role, the company's enabled features, and whether the connection has write access.

Does Clarier MCP expose MCP resources?

No. The current connector exposes MCP tools rather than browsable MCP resources. Seeing zero resources in an MCP client is expected.

Can I use the endpoint with another MCP client?

Clarier uses the standard remote MCP Streamable HTTP transport, but an external client must also be supported by Clarier's OAuth configuration. Contact dev@clarier.ai before configuring a client that is not available through an approved directory listing.

Technical details

The endpoint alone is not sufficient for every third-party client. Clarier uses pre-registered OAuth client configuration for supported clients rather than public dynamic client registration. Contact Clarier before attempting a manual integration.

Support