--- title: "Connect ChatGPT to FidelicAI" 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-15" --- # Connect ChatGPT to FidelicAI 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 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. ## 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 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. - A downloadable skill or local plugin folder does not by itself establish an authenticated server connection. [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. ### 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. ### 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. ### 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. ### 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. [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. ### 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. ### 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. ### 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. [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 > 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. ## 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. > Help me set up FidelicAI in ChatGPT. Read [the platform-specific setup instructions](https://fidelic.ai/connect/chatgpt/AGENT.md) first. Check whether access is released for my exact AI surface before attempting setup. Use only the supplied official listing or endpoint. Help with the permitted steps and leave sign-in, secrets, and required consent to me. Verify one read-only expertise call; if access is unavailable, tell me the exact next step and offer the public migration skill. [Read setup instructions for your AI](https://fidelic.ai/connect/chatgpt/AGENT.md). Retain a minimal record: platform and surface, account context, setup status, check date, tool used, guidance identifier and release when returned, unresolved limits, and next action. Reading 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. ## 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. [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 - [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 15, 2026. ## Citation FidelicAI. “Connect ChatGPT to FidelicAI.” Updated October 15, 2026. [Canonical record](https://fidelic.ai/connect/chatgpt).