OpenAPI spec in.
Grok Build
Build a Grok-ready MCP server from OpenAPI.
If your API already has OpenAPI, you should not hand-write the first Grok MCP server. Generate the server, inspect the safety report, download the pack or create a private repo where enabled, and deploy only the reviewed hosted endpoint.
01Details
The lead-funnel artifact
Agent-ready tool inventory out.
Safety report out.
Generated MCP server out.
Grok, ChatGPT, Claude, Hermes, OpenClaw, Cursor, VS Code, Cline, and Continue install files out.
02Details
Why this is different from a random bot PR
The generated repo belongs to the API owner.
External writes are disabled by default.
Draft PR plans are generated for customer-owned repos only.
No xAI repository contribution is required or attempted.
03Details
What to QA
The MCP server builds and exposes the expected tool list.
The Grok connector JSON contains a hosted HTTPS URL and a non-empty safe allowlist.
SDK snippets point to https://api.x.ai/v1 only when using the xAI OpenAI-compatible API path.
Secrets and hosted URL query strings are removed from generated manifests and snippets.
04Details
Upgrade path
Free preview: generate, download, and review the pack.
GitHub connected, where enabled: create a private generated repo after GitHub auth and explicit approval.
Hosted MCP: publish a reviewed public HTTPS endpoint when Sourced hosting is enabled.
Production release: keep repo writes, package publishing, and hosted connector rollout behind explicit owner approval.