Grok Codex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | No | xAI API key for authentication | |
| XAI_BASE_URL | No | Base URL for xAI API | https://api.x.ai/v1 |
| GROK_CODEX_MODEL | No | Default model to use | |
| GROK_CODEX_API_MODE | No | API mode: 'chat' or 'responses' | |
| GROK_CODEX_AUTH_MODE | No | Force authentication mode (e.g., 'api_key') | |
| GROK_CODEX_CONFIG_DIR | No | Configuration directory | |
| GROK_CODEX_USER_CONSENT | No | Set to '1' to grant user consent at process level |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| grok_codex_consent_statusA | Read explicit-consent state. Cannot grant consent. |
| grok_codex_provider_statusB | Check credentials and readiness without exposing secrets. |
| grok_codex_chatC | Chat with Grok. Prefers SuperGrok OAuth; falls back to XAI_API_KEY. |
| grok_codex_list_modelsA | List curated (and optionally live) models. |
| grok_codex_login_statusA | SuperGrok / xAI OAuth login status (no secrets). |
| grok_codex_login_startC | Start xAI device-code OAuth (SuperGrok / Premium+). Returns verification URL. |
| grok_codex_login_completeA | Poll until device authorization completes; saves tokens. |
| grok_codex_logoutA | Delete local SuperGrok OAuth tokens (does not revoke on xAI). |
| grok_codex_doctorB | Quick local diagnosis: consent, credentials, default model. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: chat, auth flow steps, consent check, diagnosis, model listing, and provider status. No overlap in functionality despite some status-oriented tools.
All tools share the prefix 'grok_codex_' and mostly follow noun or verb_noun patterns. Minor inconsistency: 'logout' breaks the 'login_*' pattern of the auth group.
9 tools is well-scoped for an AI chat assistant with authentication needs. Each tool earns its place, covering chat, auth lifecycle, status checks, and model listing.
The tool set covers the obvious needs: chatting, authentication (start/complete/status/logout), consent management, diagnosis, provider status, and model listing. No dead ends for core workflows.