OpenAPI 3.0 or 3.1 in YAML or JSON.
MCP generator
Generate a Grok Bot MCP server.
A Grok Bot connector needs a public HTTPS MCP server and a tight tool allowlist. Sourced generates the MCP package, the Grok install files, and the review report from the same OpenAPI input.
01Details
Inputs
Optional hosted MCP URL if you already deployed the generated server.
A direct download with the generated files, plus deploy guidance for your own GitHub repo or host.
API auth metadata from the OpenAPI security schemes.
02Outputs
Outputs
connector.grok.json for reviewable remote MCP configuration.
connector.grok.xai-sdk.py for xAI's native SDK shape.
connector.grok.openai-sdk.py for the OpenAI-compatible xAI Responses API shape.
connector.grok.curl.sh for a raw HTTP smoke test.
agent-readiness.md and harness tests so the owner can see what is safe before publishing.
03Details
Why generation beats hand-writing
Tool names stay tied to operationId instead of drift-prone docs copy.
Path, query, and body inputs come from the OpenAPI schema.
Sensitive reads and destructive operations are flagged before they are exposed.
Regeneration catches OpenAPI drift every time the API changes.
04Details
What is not automated yet
Sourced does not open PRs against xAI repositories.
Sourced does not enable every tool by default for Grok.
Hosted remote MCP must be on a public HTTPS URL; Sourced shows the exact blocker until that exists.
OAuth consent, callback URLs, token storage, and refresh behavior still need owner review before a hosted agent connector goes live.