Destination type
First-party connection
GrokCore platform path•Path checked
Grok custom connector / Remote MCP
Grok's custom connector path lets an account add a remote MCP server. It is a connection workflow, not evidence of a public marketplace listing or catalog admission.
The brand reference above links to an official platform source. EveryMCP is an independent directory and is not endorsed by this platform.
Eligibility and connection boundary
The connection needs a server URL and label, with authorization or headers when the server requires them. xAI's remote-MCP documentation identifies Streaming HTTP and SSE as supported transports.
Review or publication path
The checked connector and remote-MCP docs describe how to connect a server; they do not claim a public directory review or publication process. Treat a successful custom connection as client setup only.
Cost and terms
No connector listing fee is stated in the checked xAI docs. API, account, or model usage terms remain account-specific.
Preparation checklist
- 1.Expose a stable HTTPS endpoint and confirm the transport is Streaming HTTP or SSE before adding it.
- 2.Set a precise server label, authorization method, and minimum headers or scopes; never paste production secrets into a shared test.
- 3.Exercise tools with read-only fixtures first, then test write boundaries and failure responses.
- 4.Record the connector URL, client account, test date, and removal steps as connection evidence rather than a listing receipt.
Open questions
- • Which account tiers and product surfaces expose custom connectors at the time of connection.
- • Any separate review or publication path beyond adding a connector to an account.
Sources checked
2026-09-22Receipt boundary: A connection, a submitted PR, or a registry record does not prove marketplace approval. Keep the platform response, version, review state, and rollback plan with the release evidence.