Open source · Local first · MCP native

One Grok gateway.
Every coding agent.

UniGrok lets Codex, Claude, VS Code, and other MCP clients share a server-side Grok connection without copying your xAI credential into every editor.

01

One server-side credential boundary

02

API and subscription CLI planes stay distinct

03

Codex-owned integration and release gates

example · local command session
$ curl -fsS localhost:4765/healthz
 example response: {"status":"healthy"}

$ codex mcp get grok
transport    Streamable HTTP
endpoint     localhost:4765/mcp
tools        agent + research jobs
credential   server-side only
# each client sends its own X-Client-ID
Published route contract · Not a live runtime probe
Public project info
Static metadata available
Control center
GitHub role-gated
Remote MCP
Private OAuth · API plane only

Never send an xAI API key to this website. This public site holds no credentials and requests none.

One service, clear trust zones

Local power without making your laptop the product.

The public site teaches the project. The protected control center is for approved contributors. UniGrok itself keeps credentials and model execution behind an MCP boundary.

01

Shared MCP gateway

Connect multiple IDE agents to one stable endpoint with per-client attribution and server-held credentials.

POST /mcp
02

Two execution planes

The xAI API plane and Grok CLI subscription plane have separate catalogs, sessions, costs, and failover rules.

api ≠ cli
03

Supervised collaboration

Agents and humans can propose changes while deterministic tests and Codex-owned landing keep main coherent.

review → verify → land
04

Forge evolutionary search

Verified swarm and evolutionary code search runs in the local contributor Forge, not in the browser.

become a contributor →
IDE agents
Codex · Claude · VS Code
UniGrok MCP
Routing · sessions · policy
Grok planes
xAI API · local CLI

Start with the real boundary

Run locally. Verify directly. Then connect your IDE.

Initialization prints the supported xAI API and SuperGrok CLI credential paths. Complete at least one before expecting real agent calls to succeed.

git clone https://github.com/djtelicloud/grok-mcp-server.git
cd grok-mcp-server
uv run python main.py init
# Choose an API or CLI credential path; then:
docker compose up --build -d

Help build the gateway

Contributors get a control plane. Visitors get a clear front door.

GitHub login establishes contributor identity. Every protected request performs a fresh server-side role check against this repository before returning project data.