---
title: Grok custom MCP connector setup
description: Follow Grok's documented custom-connector path and verify a permitted Phasoric knowledge read before relying on it.
slug: mcp-grok
path: /mcp-grok
section: MCP setup
availability: documented-setup
nav_order: 6.9
canonical_url: https://developers.phasoric.com/mcp-grok
markdown_url: https://developers.phasoric.com/mcp-grok.md
mirror_url: https://phasoric.com/developers/mcp-grok
---
# Grok custom MCP connector setup

Use a Premium-or-higher Phasoric account and [prepare an authorized vault](https://developers.phasoric.com/mcp-client-setup). Free hosted-intelligence credit packs do not enable MCP.

## Use the custom connector path

Where your Grok account exposes custom connectors, open its connectors page, create a custom entry, and supply:

```text
https://phasoric.com/api/mcp
```

Complete the required Phasoric authentication and inspect consent. Do not supply Dropbox, Google Drive or GitHub credentials to the connector. On Grok Business and Enterprise, an administrator must first make the connector available to the team.

Sources checked September 17, 2026: official [custom connector instructions](https://docs.x.ai/grok/connectors) and [team connector management](https://docs.x.ai/grok/connector-management). They establish the client configuration path, not a completed Phasoric authentication or interoperability test. Availability and policy depend on the Grok account; Phasoric is not claimed to be a built-in catalog connector.

## Verify before relying on it

Ask Grok to list the Phasoric vaults it can access, search a returned mapping for a project decision, and read that note with its source path. A visible connector or tool list alone does not prove an authorized note read.

Keep initial access read-only. Phasoric's [write contract](https://developers.phasoric.com/mcp) requires a preview, your approval and mapping-specific authority before applying changes. This guide does not establish Grok write-approval behavior or unattended renewal reliability.

## API workflows are separate

The [Grok API remote MCP interface](https://docs.x.ai/developers/tools/remote-mcp) documents Streaming HTTP/SSE, authorization and tool allowlists. It requires separate application-side credential handling and is not interchangeable with signing in to a Grok custom connector. No ready-made Phasoric API integration is claimed here.