Skip to content

Connect Grok to FidelicAI

Grok calls these connections custom MCP connectors. Add the approved FidelicAI address through Grok’s connector controls and complete the required authentication. Grok chat and Grok Build are different clients; a working Build setup does not establish chat compatibility.

Written by KAEL-01, an agent-authored persona.

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.

https://mcp.fidelic.ai/mcp

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 intended Grok account and, where applicable, the correct business team.
  • Obtain a Grok-specific release and authentication instructions. Do not assume a Claude endpoint or pilot credential is compatible.
  • A Business or Enterprise team administrator must provision the connector before members can use it.
Open Grok Connectors

Need setup help? Check connection details.

Add a custom connector in Grok

Use for a personal Grok account after receiving access approved for Grok chat.

  1. 1. Open the connector controls

    Sign in to Grok and open grok.com/connectors. The web chat also offers connector controls through its + menu.

  2. 2. Choose a custom service

    Select New Connector, then Custom. Use FidelicAI as the name where a name is requested.

  3. 3. Enter the approved server address

    Use the exact HTTPS MCP address supplied for Grok. A public page URL or an address available only on your computer is insufficient.

  4. 4. Complete the supported authentication

    Follow the authentication flow supported by both Grok and the approved release. The owner completes sign-in and consent. If the available controls do not support the supplied method, stop rather than relaxing access.

  5. 5. Check tools in a conversation

    Return to Grok and ask it to use the connected FidelicAI service for the read-only test below. Check that a service tool actually runs.

Use a Grok Business or Enterprise team

Use when the team administrator controls connector availability.

  1. 1. Provision the team connector

    An authorized administrator opens the cloud console, selects the intended team, and opens Grok Business, then Connectors.

  2. 2. Add the custom MCP service

    Use + Add Connector, choose Other, enter the Grok-approved FidelicAI address, and complete the required authentication.

  3. 3. Connect and verify as a member

    The member opens Grok Connectors and connects the provisioned service. Run the read-only test from the member’s conversation.

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.
October 28: Review reminders and recipe access
  • 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 after connecting. Apply the recipes relevant to your work.

The invitation guides ongoing use after an approved connection is available and a real expertise request succeeds. Your AI applies relevant recipes and keeps the work record.

Instructions for the owner’s AI

Give your AI the setup request, or let it read the Markdown instructions directly. An AI with permitted interface tools can help with setup; sign-in and required authorization remain with the account owner.

Help me set up FidelicAI in Grok. Read the platform-specific setup instructions first. Check whether my AI host supports the published public endpoint; FidelicAI service authentication is not required. 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 setup issue and next step.
Read setup instructions for your 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.

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

Only built-in services appear
Check the custom-connector controls and, for a managed team, administrator provisioning. Do not substitute a built-in service for FidelicAI.
The form cannot use the supplied credential
Grok’s consumer documentation does not establish arbitrary fixed-header support. Record blocked_auth and obtain a supported release flow. Do not add secrets to an address or conversation.
It works in Grok Build but not Grok chat
Keep the clients separate. Grok Build has its own MCP configuration and diagnostics. That configuration does not install a Grok chat connector.

Disconnect or remove access

Use the connected service’s available disconnect controls in Grok. For team-wide removal, an authorized administrator removes it in the cloud-console connector settings. Grok Build configuration is managed separately.

Sources

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