---
title: "Connect ChatGPT to FidelicAI: instructions for the owner’s AI"
description: "Set up FidelicAI through a ChatGPT plugin or approved custom MCP connection. Follow owner and agent steps for access, authentication, verification, and fixes."
canonical: "https://fidelic.ai/connect/chatgpt"
lastUpdated: "2026-10-28"
---

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

ChatGPT uses plugins to package skills and MCP connections. Install the released FidelicAI plugin when available, or use a custom MCP connection only when your invitation explicitly supports ChatGPT. Installation and service authentication are separate steps.

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 the ChatGPT account and workspace approved for the connection. Workspace policy can restrict installation or service access.
- For the directory route, obtain the actual FidelicAI listing link. For the custom route, obtain a ChatGPT-approved server address and authentication instructions.
- Verify that the connected host can retrieve an actual cookbook recipe.

[Open ChatGPT Plugins](https://chatgpt.com/plugins).

## Install the released ChatGPT plugin

Use this route once FidelicAI supplies a plugin listing available to your account. No listing is released yet.

### 1. Open Plugins in the intended workspace

Sign in to ChatGPT and open Plugins. Check the active workspace before installing.

**Done when:** The plugin directory belongs to the intended account and workspace.

### 2. Open the supplied FidelicAI listing

Follow the official listing link and inspect its publisher, capabilities, and connection requirements. If it is absent or unavailable, use the access route specified in your invitation.

**Done when:** The listing and publisher match the FidelicAI release details.

### 3. Install the plugin

Use the listing’s plus control. Complete any permitted workspace installation step. An installed bundle can still need a service connection.

**Done when:** The plugin appears as installed; connection status is checked separately.

### 4. Connect the service when prompted

Follow the plugin’s service connection flow. Some plugins request authentication at installation; others request it on first use. The owner completes sign-in and reviews requested access.

**Done when:** The required service connection completes without sharing credentials in the chat.

### 5. Start a new chat and request FidelicAI

Ask ChatGPT to use the installed FidelicAI plugin for the read-only check below. If the plugin appears in the @ picker, you can select its actual displayed name.

**Done when:** A new conversation can discover and invoke the intended expertise tools.

[OpenAI: install, use, and remove plugins](https://learn.chatgpt.com/docs/plugins).

## Add an approved custom MCP connection

Use this alternative only with a FidelicAI invitation naming ChatGPT custom MCP support. This does not publish a plugin to the public directory.

### 1. Open the custom connection form

In ChatGPT Plugins, use the plus control and choose Add custom MCP server. If the option is unavailable, check workspace policy rather than switching accounts without approval.

**Done when:** The custom MCP form is available in the intended workspace.

### 2. Enter the supplied service details

Use FidelicAI as the display name where a name is requested. Enter the exact server address and connection settings supplied for ChatGPT. Use the release’s supported authentication flow.

**Done when:** The form matches the approved endpoint and authentication instructions.

### 3. Review and create the connection

Read the displayed risk and access notice. Continue only with the owner’s approval, then use Create as a plugin. If the form cannot support the supplied authentication, stop and record the incompatibility.

**Done when:** The custom connection exists under the owner’s account; no public directory listing is implied.

### 4. Open a new conversation and verify tools

Ask ChatGPT to use the new connection for the read-only check below. If the tools are not available, check connection status and workspace access before retrying.

**Done when:** A real expertise-tool response is available in the new conversation.

[OpenAI: create a test plugin with an MCP connection](https://developers.openai.com/plugins/build/plugins#create-and-test-a-plugin-locally-with-an-mcp-server).

## 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": "chatgpt",
  "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 FidelicAI plugin cannot be found

Check whether you have a released listing or an approved custom-MCP invitation. A future plugin is not searchable merely because the website describes it.

### Installed, but no expertise tools are available

Check the service connection and active workspace, then start a new chat. Plugin installation and MCP authentication are separate.

### The authentication option does not match the invitation

Record blocked_auth. Do not convert a protected service to unauthenticated access or paste a bearer credential into the conversation.

## Disconnect or remove access

Open the plugin’s controls to uninstall it where your account permits. Open the separately connected MCP service and disconnect it too if you want to revoke that connection. Uninstalling the plugin does not necessarily disconnect its MCP integration. Workspace-managed plugins may require an admin.

[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

- [OpenAI: install, use, and remove plugins](https://learn.chatgpt.com/docs/plugins)
- [OpenAI: create a test plugin with an MCP connection](https://developers.openai.com/plugins/build/plugins#create-and-test-a-plugin-locally-with-an-mcp-server)

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 ChatGPT to FidelicAI: instructions for the owner’s AI.” Updated October 28, 2026. [Canonical record](https://fidelic.ai/connect/chatgpt).
