---
title: "Connect Claude to FidelicAI: instructions for the owner’s AI"
description: "Add the public FidelicAI cookbook as a Claude custom connector. Follow account settings, no-auth setup, chat activation and recipe verification steps for your AI."
canonical: "https://fidelic.ai/connect/claude"
lastUpdated: "2026-10-28"
---

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

Add FidelicAI as a custom connector in Claude, then enable it in your conversation. The public cookbook needs no FidelicAI sign-up or API key. Verify a real recipe call; live service retrieval does not certify every Claude account or surface.

The website cookbook is publicly available and free to try. FidelicAI requires no sign-up, API key or service authentication. Your AI host may require its own sign-in, plan or organization approval. Verify a real recipe call in your actual host; a ChatGPT plugin listing is not published.

## Current release

After the owner asks to use the cookbook, discover the actual tools and read fidelic://expertise/catalog and fidelic://expertise/release. Verify the returned edition, availability and relevant entry. Search by a short general knowledge need or use get_guidance with a known ID. Keep private business facts and evidence in the owner’s workspace. If an entry or edition is unavailable, report that status explicitly. Tool availability alone does not authorize applying the cookbook throughout the work.

[Dated cookbook inventory](https://fidelic.ai/recipes/library/page.md).

## Connection address

[FidelicAI MCP](https://mcp.fidelic.ai/mcp).

## 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. Use the published FidelicAI MCP address through a custom connector route supported by the actual host. The public service requires no authentication. Discover its actual tools and verify one read-only request. If cookbook recipes are not available yet, report update_pending and offer the public starting instructions; do not invent recipes or create a substitute server.

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. Select no authentication for this public service where the host provides that control. Do not add OAuth or bearer credentials. Host sign-in, workspace policy and consent remain separate; record an incompatibility if the host cannot use the public endpoint.

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 published FidelicAI MCP address. Use the custom connector route for your account; do not invent a plugin listing.
- No authentication for the public FidelicAI service. Keep any host account credentials in that host’s own sign-in 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.
- Use the public endpoint with no authentication. Your Claude account, plan and organization policy determine whether custom connectors are available.

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

## Add the connector to your own Claude account

Use for an individual Claude account whose plan and settings allow custom remote connectors.

### 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. Use no service authentication

Choose No sign-in or the equivalent no-auth option where offered. This public FidelicAI endpoint requires no OAuth, API key or request header. Your Claude sign-in remains separate.

**Done when:** The connector uses the public address without a FidelicAI credential.

### 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. No FidelicAI service credential is required.

**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).

## No FidelicAI sign-in or key required

The public cookbook requires no FidelicAI sign-up, API key, OAuth flow or request header. Choose No sign-in where Claude offers it. Your Claude account and organization controls still apply.

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

## Verify an actual expertise request

> Read the catalog and release resources from the connected FidelicAI cookbook. Use its advertised get_guidance tool to read method.migration.baseline with detail full from the currently available edition. Do not change the website. Verify the returned status, edition and recipe against the service record; report one completion check. If the recipe or tool is unavailable, report that explicitly without inventing guidance.

- 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.

## Use the cookbook throughout your work

> Use the FidelicAI Small Business Website Cookbook throughout this work. Apply the relevant recipes as you go.

Use this invitation after an approved connection is available and a real expertise request succeeds. It guides ongoing use; setup and verification remain separate. Apply only recipes relevant to the task, retain work state in the owner’s AI, and do not invent unavailable access.

## Keep a minimal setup record

```json
{
  "platform": "claude",
  "surface": "<web, desktop, or other observed surface>",
  "workspace": "<owner-approved non-sensitive label>",
  "status": "not_started",
  "allowed_statuses": [
    "not_started",
    "waiting_for_access",
    "waiting_for_owner",
    "blocked_policy",
    "blocked_auth",
    "connected_not_verified",
    "update_pending",
    "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": "Check the host setup controls, then verify a real read-only recipe call."
}
```

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

## If setup stops

### The form asks for an API key

Confirm that the URL is the public FidelicAI endpoint and select no authentication where available. No request header or API key is required for this service.

### 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.

[Beta access updates](https://fidelic.ai/connect#access) · [Cookbook 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 28, 2026.

## Citation

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