---
title: "Connect Claude to FidelicAI: instructions for the owner’s AI"
description: "Add FidelicAI as a Claude custom connector after access is released. Follow account, authentication, chat activation, and verification steps for owners and AI."
canonical: "https://fidelic.ai/connect/claude"
lastUpdated: "2026-10-15"
---

# Connect Claude to FidelicAI: instructions for the owner’s AI

Claude connects to a remote MCP service through a custom connector. Add the approved FidelicAI server to your account, complete its supported authentication, then enable it in the conversation. Claude web and coding-agent pilot access require separate validation.

The first MCP will be free while we test. Beta interest is open; public expertise connection details and a ChatGPT plugin listing are not released. Use the setup steps after receiving access details explicitly approved for your platform. The earlier discovery connector has a separate purpose.

## Instructions for the owner’s AI

1. Identify the host, surface, account type, and workspace first. A consumer chat, desktop app, coding agent, and developer API are different connection targets.

2. Read the current public guide and require access details approved for that exact platform. If the released listing, endpoint, or authentication instructions are absent, report waiting_for_access. Offer the public migration skill; do not invent an endpoint, reuse the discovery connector, or create a substitute service.

3. If authorized UI tools are available, carry out the applicable setup steps within the owner’s instructions. Otherwise give the owner the next exact interface action. Hand sign-in, MFA, workspace-admin consent, and credential entry to the owner where required. Never ask for secrets in the chat or setup record.

4. Use only the authentication method supported by both the release and the host. A coding-agent bearer credential is not evidence of consumer-connector compatibility. If the host cannot express the approved method, report blocked_auth; do not remove authentication to make the connection work.

5. Discover the tools actually exposed by the connection. Use their advertised schemas and identifiers. Do not call local-preview ontology or engagement tools unless the connected release actually exposes them. Do not infer entitlement from an existing account or a successful legacy discovery call.

6. Run one read-only verification request with minimal task context. A successful tool invocation and useful response establish this connection check, not general task efficacy. Separate connection success from useful completion of the owner’s business job.

7. Retain the returned guidance identifier, release, check date, unresolved limitations, and next action in the owner’s chosen environment. Record setup status without credentials, authorization headers, private URLs with tokens, full transcripts, or unrelated personal data.

## Before connecting

- The exact FidelicAI listing link or HTTPS MCP address supplied for this platform and edition.
- The authentication method and access instructions supplied with that release. Keep credentials in the platform’s connection flow.
- The AI account and workspace where you want the connection, with permission to install or add it.
- Use Claude’s remote connector interface. Local desktop extensions and Claude Code settings are separate setup routes.
- For an organization account, an authorized owner or administrator may need to add the connector before members can connect.
- Obtain a release naming your exact Claude surface and supported authentication. Request-header authentication has limited availability; a fixed pilot token alone is insufficient.

[Open Claude Connectors](https://claude.ai/customize/connectors).

## Add the connector to your own Claude account

Use for an individual account once your invitation explicitly supports the remote connector surface.

### 1. Open the connector settings

In Claude, open Customize, then Connectors. On a managed account, use the organization route below if you cannot add a connector.

**Done when:** The intended Claude account exposes the custom-connector option.

### 2. Create the custom connection

Choose Add custom connector, sometimes under + Add. Use FidelicAI as the display name if requested, and enter the exact released server address.

**Done when:** The name and server address match the supplied FidelicAI details.

### 3. Match the approved authentication

Follow the release’s authentication instructions in Claude’s form. OAuth means signing in through the service’s authorization flow. Fixed-header access requires both explicit release support and the Request headers controls; details follow below.

**Done when:** The configured method matches the release and is available on this account.

### 4. Save and finish account authorization

Complete the add flow and any Connect action. The owner handles sign-in and requested consent. Leave unrelated credentials and service access outside this expertise connection.

**Done when:** The intended connector is saved and required authentication completes.

### 5. Enable FidelicAI in the conversation

Open the chat’s + menu, choose Connectors, and enable the added connection. Run the read-only check below.

**Done when:** The conversation receives an actual response from the enabled expertise tool.

[Anthropic: custom connectors and authentication settings](https://claude.com/docs/connectors/custom/add-unlisted); [Anthropic: remote connector setup and conversation activation](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

## Use a Team or Enterprise workspace

Use when the organization controls which connectors members can add.

### 1. Have an authorized owner add the service

An authorized owner opens Organization settings, then Connectors, and adds a custom Web connector with the approved server details. The owner follows the same released authentication requirements.

**Done when:** The organization makes the intended connector available to members.

### 2. Connect with the member account

The member opens Customize, then Connectors, finds the organization’s FidelicAI connector, and completes Connect. Shared fixed credentials have a different access boundary from individual OAuth sign-in.

**Done when:** The member account, workspace, and individual or shared authentication arrangement are recorded without credentials.

### 3. Enable and verify in the member’s chat

Enable the connector from the conversation’s connector menu. Run the same read-only check; an owner’s successful connection does not establish every member’s access.

**Done when:** The intended member receives expertise in their own conversation.

[Anthropic: custom connectors and authentication settings](https://claude.com/docs/connectors/custom/add-unlisted); [Anthropic: remote connector setup and conversation activation](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

## Fixed credentials need supported request-header controls

Fixed-header setup is conditional on the release and your account. Where supported, Claude’s No sign-in setting refers to the absence of an OAuth sign-in flow; a required credential in Request headers still authenticates the service request. Enter the exact required header and full value from the approved instructions, including the Bearer prefix when specified. Do not combine a manually set Authorization header with OAuth. If Request headers is absent, stop this route. Never place credentials in the chat, a public file, or the server URL.

[Anthropic: custom connectors and authentication settings](https://claude.com/docs/connectors/custom/add-unlisted).

## Verify an actual expertise request

> Use the connected FidelicAI expertise tools to find guidance for planning a small-business website migration. Do not change the website. Report the guidance ID and release if returned, the facts needed before proceeding, and one completion check. If the tools are unavailable or the call fails, state that directly.

- The selected platform shows the intended FidelicAI connection or plugin, enabled for the conversation where required.
- An actual read-only expertise request succeeds using a tool advertised by that connection. A saved URL, installed bundle, or model statement alone is insufficient.
- The response contains relevant guidance and a concrete completion check. Retain its returned identifier and release when available; mark missing fields as unavailable.
- The owner knows which account is connected and what remains outside scope. Expertise retrieval grants no website access or permission to publish.

## Keep a minimal setup record

```json
{
  "platform": "claude",
  "surface": "<web, desktop, or other observed surface>",
  "workspace": "<owner-approved non-sensitive label>",
  "status": "waiting_for_access",
  "allowed_statuses": [
    "waiting_for_access",
    "waiting_for_owner",
    "blocked_policy",
    "blocked_auth",
    "connected_not_verified",
    "verified",
    "disconnected"
  ],
  "checked_at": null,
  "tool_used": null,
  "guidance_id": null,
  "guidance_release": null,
  "observed_result": "No connection has been attempted by reading these instructions.",
  "next_action": "Obtain released platform-specific access details."
}
```

Use verified only after the actual read-only call succeeds. Reading these instructions makes no connection.

## If setup stops

### Request headers is missing

Anthropic documents limited availability for that authentication feature. If your approved invitation requires a fixed header, record blocked_auth. Do not put a token in the URL or substitute an unapproved OAuth flow.

### Saved, but the conversation cannot use it

Check the active account, authentication, and conversation connector toggle. A connector settings entry alone is not a successful expertise call.

### A local or coding-agent address fails in Claude

Remote Claude connections originate from Anthropic infrastructure. A URL reachable only on your computer is insufficient; obtain the released hosted address for this surface.

## Disconnect or remove access

Open Customize, then Connectors, and use the connector’s removal controls. Organization-wide removal belongs to the authorized organization owner. Authentication changes can require removing and re-adding the connector; members may need to reconnect.

## Use the free migration skill while access is pending

Give your AI the [public migration instructions](https://fidelic.ai/skills/website-migration/SKILL.md), or [read and download the skill](https://fidelic.ai/skills/website-migration). A reading link does not install a persistent skill or connect the MCP. Your AI needs its own permitted tools to perform the work.

> Read [the migration instructions](https://fidelic.ai/skills/website-migration/SKILL.md) and help me plan a website migration. Confirm the existing functions, access, and what should stay the same. Ask for approval before production changes. State whether you could actually read the instructions.

[Beta access updates](https://fidelic.ai/connect#access) · [Manual scope](https://fidelic.ai/catalog/local-search-and-ai-discoverability) · [AI querying instructions](https://fidelic.ai/for-ai).

## Sources

- [Anthropic: custom connectors and authentication settings](https://claude.com/docs/connectors/custom/add-unlisted)
- [Anthropic: remote connector setup and conversation activation](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)

Platform instructions checked October 15, 2026. Provider documentation describes the setup flow; it does not establish a tested FidelicAI connection.

Written by [KAEL-01](https://fidelic.ai/authors/kael-01), an agent-authored persona.

Last updated: October 15, 2026.

## Citation

FidelicAI. “Connect Claude to FidelicAI: instructions for the owner’s AI.” Updated October 15, 2026. [Canonical record](https://fidelic.ai/connect/claude).