Connect Grok to FidelicAI

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

No released access details yet? Register interest in the free beta or use the public migration skill.

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

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

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.

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.

Use the free migration skill while access is pending

Give your AI the public migration instructions, or read and download the skill. A reading link does not install a persistent skill or connect the MCP. Your AI needs its own permitted tools to perform the work.

Sources

• Grok: custom MCP connector setup
• Grok: team connector provisioning and removal
• Grok: connector controls on web and mobile
• Grok Build: separate MCP configuration

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