Does the connector require a Clarier API key?

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

Does Claude receive everything in our Clarier workspace?

No. The connector returns only what a requested tool asks for, within the connected user's company, role, and enabled features.

Can a prompt switch the connector to another company?

No. The company is fixed to the authorized connection. Switching requires reconnecting.

Can Claude change records on its own?

No. Supported writes use a prepare, review, and confirm flow, and are committed only after the user explicitly approves the proposed fields.

Clarier MCP Connector

Overview

The Clarier MCP connector lets Claude use a customer’s Clarier workspace as the source of truth for their AI tool inventory, vendor assessments, and request status. It is hosted and maintained by Clarier Technologies, LLC, and uses the Model Context Protocol’s Streamable HTTP transport with OAuth 2.1 authentication. No API keys are entered into Claude.

Clarier MCP connector at a glance
Server type	Remote MCP server, hosted by Clarier
Authentication	OAuth 2.1 with explicit user consent
Transport	Streamable HTTP
Access model	Existing Clarier company, role, SSO, and feature permissions
Actions	Read, plus confirmation-based writes when enabled
Tenant model	One selected Clarier company per connection
API key required	No

Connect in Claude

In Claude, open Settings → Connectors and add Clarier.
Sign in on the Clarier authorization page with your existing Clarier account.
Choose the Clarier company this connection should use.
Review the requested access and grant write access only if you want Claude to prepare and submit supported changes.
Approve the connection and return to Claude.

An active Clarier account, membership in the company you are connecting, and connector enablement by a Clarier administrator are required. Companies enforcing Microsoft SSO must authorize from an SSO session.

What it does

Look up AI tools in the connected company’s inventory and their governance status.
Read an existing Clarier vendor assessment for a named tool.
Check the status of an AI tool request and approvals waiting on the user.
Summarize governance posture, and — for administrators, where the feature is enabled — AI usage and compliance snapshots.
Prepare and, after user confirmation, submit a new AI tool request when write access is enabled.

Permissions and consent

The tool list is generated per request from the connected user’s role and the company’s enabled features. Administrators see more than standard users.
The company selected during authorization is bound to that connection; a prompt cannot switch it.
Clarier rechecks membership, role, SSO policy, feature availability, and connection status on every request.
Companies may run the connector read-only.

Write actions

Supported writes follow a prepare, review, and confirm flow:

Claude prepares the action without changing any Clarier record.
Claude shows every field that will be submitted.
The user can revise values and have the action prepared again.
The change is committed only after the user explicitly approves it.

Security and data handling

OAuth 2.1 with user consent; each connection is scoped to one Clarier company and the connected user’s role.
Record lookups are scoped to the connected company; cross-tenant access is prevented.
Tool results are returned into the Claude conversation and handled under the customer’s agreement with Anthropic.
The connector does not read unrelated Claude conversations, memory, or history, and customer data is not used to train models.
Clarier does not persist raw read-tool prompts or results. Connection records, rate-limit metadata, and audit events are retained to operate and audit the service.
Per-company daily request limits apply.

Manage or revoke access

Disconnect in Claude under Settings → Connectors, and revoke the authorization in Clarier under Connected AI clients. Revocation takes effect on the next connector request. Each connection is bound to one company, so using a different company requires reconnecting.

Support

Need help with the Clarier connector?

Contact Clarier for connection support, company enablement, or security-review questions.

Email dev@clarier.ai

FAQ

Does the connector require a Clarier API key?: No. Users authenticate with OAuth 2.1 using their existing Clarier account.
Does Claude receive everything in our Clarier workspace?: No. The connector returns only what a requested tool asks for, within the connected user's company, role, and enabled features.
Can a prompt switch the connector to another company?: No. The company is fixed to the authorized connection. Switching requires reconnecting.
Can Claude change records on its own?: No. Supported writes use a prepare, review, and confirm flow, and are committed only after the user explicitly approves the proposed fields.