Grok does not have a self-serve Featured catalog listing (GitHub, Notion, etc. are partner-only). Any Grok user can add Zephex via Bring Your Own MCP at grok.com/connectors → New Connector → Custom. OAuth links your Zephex account — you do not paste an API key into Grok.
Official Grok MCP documentation: xAI Grok connectors docs
Without MCP, your agent guesses project layout and misses supply-chain risk. Zephex connects one hosted endpoint so every session gets the same ten tools — no per-machine npm installs, no version drift across the team.
Matches the published CLI (mcp-proxy/src/commands/setup.ts). One command signs you in, writes the correct transport, and verifies 10 tools.
Account teardown: logout vs disconnect · Connect MCP walkthrough
Search docs for “where is my MCP file” — the answer is always: run list first, then open the path it prints.
Documented paths: Run npx -y zephex@latest list
Full comparison: HTTP vs stdio · npx zephex reference
Grok uses a two-screen Custom Connector flow. Screen 1 is the server URL; Screen 2 appears only if Grok asks for OAuth credentials.
Common mistake: putting https://zephex.dev/oauth/authorize in Server URL. Grok needs https://zephex.dev/mcp — OAuth discovery handles authorize/token endpoints.
Paste this into the Custom connector Server URL field. This is the MCP endpoint Grok calls after OAuth.
https://zephex.dev/mcpOptional second screen. Use the shared public PKCE client — same pattern as other hosted MCP vendors.
Client ID: 2JrCMEKyOdY1YDZxInqTamSGNSCX9DaSClient Secret: (leave blank)Authorization Endpoint: https://zephex.dev/oauth/authorizeToken Endpoint: https://zephex.dev/oauth/tokenScopes: openid profile email offline_accessToken Auth Method: none (PKCE)Tip
Featured connectors (GitHub, Notion, Linear) require an x.ai partnership — Custom MCP works for all Grok users today.
Note
Last verified: July 2026 — Custom MCP at grok.com/connectors is the supported path. Featured catalog is partner-only (x.ai/contact-sales).
Run these in a terminal when the editor UI is unclear — catches stale npm, wrong transport, and project shadows.
npx -y zephex@latest listnpx -y zephex@latest doctornpx -y zephex@latest repair# Fully quit the editor (Cmd+Q / Alt+F4), reopen, start a new agent sessionAfter saving your config, confirm Zephex is connected before you rely on it in real work.
Questions people ask when Grok does not show Zephex tools — indexed for docs search.
How do I connect Zephex to grok?
Fastest: npx -y zephex setup (browser sign-in, writes config, verifies 10 tools). Or paste manual config on this page, save, fully quit the app, reopen.
Where did setup save my grok MCP config?
Run npx -y zephex@latest list — it prints every config path on this machine that references Zephex.
grok works in terminal but not in the editor
GUI apps often lack nvm/fnm PATH. Run npx -y zephex@latest repair, ensure Node is on system PATH, fully quit the editor.
How do I disconnect Zephex from grok?
mcpcli disconnect --all or remove the zephex block manually from your config file.
You do not call tools yourself — ask your agent in plain language. Try these once Zephex is connected:
“Use audit_headers on https://example.com and summarize the security grade.”
URL-only tool works in Grok chat without a local project path.
“Use check_package on express before I add it to package.json.”
Registry safety intel from Grok without cloning a repo.
“Use get_project_context on github:vercel/next.js — high-level stack only.”
GitHub URL is the right path when Grok cannot see your laptop folders.
Grok Custom connector cannot see your disk by default. Use github:owner/repo for public code; paste paths for private work.
These situations usually mean the setup cannot work until you fix the underlying issue:
Missing connector session on zephex.dev/cli/auth
Do not open cli/auth manually. Disconnect in grok.com/connectors → Connect again so Grok opens /oauth/authorize first (URL must include ?session=). Allow pop-ups; finish sign-in within 10 minutes.
invalid_redirect_uri or register fails
Deploy must include Grok callback in HOSTED_MCP_CALLBACKS. Run npm run verify:mcp-connectors from mcp-proxy — expect ✓ Grok authorize → cli/auth?editor=grok-connector.
OAuth screen confusion (two screens)
Screen 1 = MCP URL only. Screen 2 = optional static OAuth fields — use values in the docs block above.
Tools return no project / empty context
Include github:owner/repo in the prompt — Grok has no automatic workspace root.
Looking for API key field
Grok Custom connector uses OAuth for Zephex — create API keys only for other editors at Dashboard → API Keys.
Enable the Zephex Custom connector in Grok chat — xAI invokes these ten MCP tools server-side:
get_project_context
Reads your project structure, dependencies, scripts, env vars, and framework markers in one call. Replaces manually opening package.json, tsconfig, and multiple config files at the start of every session.
read_code
AST-based code extraction: pass a symbol name and get the implementation without reading entire files. Supports symbol lookup, batched file reads, and structural outlines for large files.
find_code
Ranked search across the repo for definitions, usages, and patterns. Faster than blind grep when the agent does not know where a symbol lives.
check_package
Live registry lookup for npm, PyPI, Cargo, and Go modules. Surfaces typosquat risk, maintainer changes, and suspicious version jumps before you run install.
explain_architecture
Generates Mermaid diagrams for auth flows, service boundaries, and module dependencies so the agent reasons about structure instead of guessing.
check_test
Turns a task description into the smallest file set to read or edit, with risk ratings and caller impact notes.
audit_headers
Grades a deployed URL for CSP, HSTS, TLS, cookies, and redirects. Returns fix snippets for common hosts (Vercel, Cloudflare, Nginx).
keep_thinking
Structured multi-step debugging: tracks hypotheses and conclusions so long investigations do not loop.
Zephex_dev_info
Expert patterns for authentication, databases, frontend frameworks, deployment, and mobile stacks when the agent needs vetted guidance.
project_memory
Persists decisions, gotchas, and conventions per project in ~/.zephex/memory (SQLite FTS5). recall before unfamiliar areas; remember after discoveries. Local stdio only on npx zephex.