This is the official documentation repository for ZeroGPU. It contains the API reference, platform guides, cookbook recipes, and SDK examples. The docs are hosted at docs.zerogpu.ai.
The Model Context Protocol (MCP) lets AI applications connect to external data sources in a standard way. Connecting your AI coding tool to ZeroGPU docs via MCP gives it live search over the full documentation. Updates to the docs are reflected automatically.
ZeroGPU docs hosts an MCP server at:
https://docs.zerogpu.ai/mcp
Step 1: Add the MCP server:
claude mcp add --transport http zerogpu-docs https://docs.zerogpu.ai/mcpStep 2: Verify: run claude mcp list and confirm zerogpu-docs appears. In a Claude Code session, ask a question about ZeroGPU; answers will be grounded in the docs.
Step 1: Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) → Open MCP settings.
Step 2: Click Add custom MCP and add:
{
"mcpServers": {
"zerogpu-docs": {
"url": "https://docs.zerogpu.ai/mcp"
}
}
}Save, restart Cursor, then ask a question about ZeroGPU in chat to verify.
Prerequisites: Node.js.
npm i -g mint
cd docs
mint devPreview at http://localhost:3000 (or the port Mintlify reports).
API playground: Each model has a live playground under API Reference → Endpoints → By model (and on its catalog page). Specs live in api-reference/openapi/playgrounds/*.openapi.json and the docs.json nav is maintained by hand. These files are committed and edited directly, there is no longer a generator.
Batch & Files playgrounds use api-reference/openapi/batch.openapi.json (hand-maintained; all /v1/files and /v1/batches paths). Playground pages live flat under api-reference/: upload-file.mdx, list-files.mdx, retrieve-file.mdx, download-file.mdx, delete-file.mdx, create-batch.mdx, retrieve-batch.mdx, list-batches.mdx, cancel-batch.mdx. These are also hand-maintained.
Docs use ASCII hyphens only (no em/en dashes). Check this by hand when editing prose.
Integrations and cookbooks: an integration's guide lives at integrations/<slug>.mdx (SDKs under integrations/sdk/). A cookbook built around one integration names it in its frontmatter, e.g. integration: litellm; general cookbooks leave it out. Nick Fury, our GTM agent, reads both from main to track docs coverage of each integration, so a merged guide or cookbook shows up there without anyone linking it by hand.
See api-reference/openapi/zerogpu.openapi.json and api in docs.json. Validate with mint validate.
- Edit
.mdxor.mdfiles in this repo. - Run
mint devto confirm the site builds. - Open a pull request with a clear description.
Mintlify docs for configuration and components.