
IMAGIN.Studio API Docs
- 1 repo stars
- Updated July 23, 2026
- IMAGIN-studio/api-docs-mcp
io.github.IMAGINstudio/api-docs-mcp is an MCP server that semantically searches IMAGIN.studio API documentation for CDN, API, and integration guidance.
About
io.github.IMAGINstudio/api-docs-mcp exposes semantic search across IMAGIN.studio’s official API documentation so your coding agent can retrieve accurate CDN rules, authentication patterns, and integration guides while you ship vehicle imagery features. SaaS founders and ecommerce developers integrating stock car photos benefit during the build integrations subphase because the MCP answers doc questions in context instead of forcing you to tab-switch through long reference sites. Install either the Python imagin-studio-api-docs-mcp package or the npm @imagin.studio/api-docs-mcp build, register the stdio server, and query by natural language during implementation. It complements but does not replace your own API keys and quota planning for the live IMAGIN.studio service.
- Semantic search over IMAGIN.studio API docs: CDN, REST API, and integration guides
- Dual publish paths: PyPI imagin-studio-api-docs-mcp and npm @imagin.studio/api-docs-mcp v0.1.17
- stdio MCP transport for Claude Code, Cursor, and other clients
- Reduces hallucinated endpoints when building automotive imagery features
- Maintained in GitHub IMAGIN-studio/api-docs-mcp with official schema metadata
IMAGIN.Studio API Docs by the numbers
- Data as of Jul 24, 2026 (Skillselion catalog sync)
claude mcp add imagin-studio-api-docs-mcp -- uvx imagin-studio-api-docs-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Package | imagin-studio-api-docs-mcp |
| Transport | STDIO |
| Auth | None |
| Last updated | July 23, 2026 |
| Repository | IMAGIN-studio/api-docs-mcp ↗ |
What it does
Semantic-search IMAGIN.studio CDN and API integration docs from the agent while wiring vehicle imagery into your app.
Who is it for?
Best when you're shipping automotive imagery, configurators, or dealer sites and already use MCP and want doc-grounded answers for IMAGIN.studio.
Skip if: Projects with no vehicle imagery needs, teams blocked from stdio MCP, or anyone expecting the server to provision IMAGIN.studio API credentials automatically.
What you get
After you add the docs MCP, your assistant pulls grounded excerpts from IMAGIN.studio documentation through MCP tools while you code the integration.
- MCP tools that return semantically matched IMAGIN.studio documentation sections
- Faster integration implementation with fewer guessed endpoints
- Dual-package install option for Python-first or Node-first solo builder stacks
By the numbers
- Server version 0.1.17
- Two packages: PyPI imagin-studio-api-docs-mcp and npm @imagin.studio/api-docs-mcp
- Transport type stdio
README.md
IMAGIN.studio API Docs MCP Server
Give your AI coding assistant instant access to the full IMAGIN.studio documentation — CDN configuration, API references, integration guides, and more.
One tool. One command. Works with every major AI coding assistant.
Quick Start
Paste this into your agent's MCP config:
{
"mcpServers": {
"imagin-docs": {
"command": "uvx",
"args": ["imagin-studio-api-docs-mcp"]
}
}
}
Or just ask your AI assistant:
Install this MCP server: https://pypi.org/project/imagin-studio-api-docs-mcp/
How It Works
- Install —
uvx imagin-studio-api-docs-mcp(no cloning, no venv, no config) - Index — On first run, clones the docs and builds a local vector index (~30 sec)
- Search — Your AI assistant calls
search_docsto find relevant documentation - Stay fresh — The index auto-updates when the upstream docs change
Everything runs locally. No API keys. No external services.
Supported Agents
| Agent | Config location |
|---|---|
| Claude Code | .mcp.json in project root |
| Claude Desktop | claude_desktop_config.json |
| Cursor | Settings > Tools & MCP |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| VS Code + Copilot | .vscode/mcp.json |
| Cline | MCP servers panel |
| Zed | ~/.config/zed/settings.json |
For detailed setup instructions for each agent, see the full setup guide on PyPI.
Alternative: npx
If your agent can't find uvx (common with GUI apps like Claude Desktop and Cursor):
{
"mcpServers": {
"imagin-docs": {
"command": "npx",
"args": ["-y", "@imagin.studio/api-docs-mcp"]
}
}
}
What You Can Ask
Once installed, try prompts like:
- "Search the IMAGIN docs for CDN cache invalidation"
- "How do I set up a custom domain with IMAGIN?"
- "Find the API endpoint for image transformations"
- "What image formats does IMAGIN.studio support?"
Packages
| Registry | Package | Install |
|---|---|---|
| PyPI | imagin-studio-api-docs-mcp |
uvx imagin-studio-api-docs-mcp |
| npm | @imagin.studio/api-docs-mcp |
npx -y @imagin.studio/api-docs-mcp |
License
Apache License 2.0 — see LICENSE.
Recommended MCP Servers
How it compares
Vendor API documentation MCP, not a generic OpenAPI linter skill or a cloud deploy integration.
FAQ
Who is io.github.IMAGINstudio/api-docs-mcp for?
It is for developers integrating IMAGIN.studio vehicle imagery who want Claude Code, Cursor, or similar agents to search official API docs locally via MCP.
When should I use io.github.IMAGINstudio/api-docs-mcp?
Use it during build when you are wiring CDN URLs, REST calls, or integration guides and need accurate doc snippets without leaving the agent session.
How do I add io.github.IMAGINstudio/api-docs-mcp to my agent?
Install imagin-studio-api-docs-mcp from PyPI or @imagin.studio/api-docs-mcp from npm v0.1.17, configure io.github.IMAGINstudio/api-docs-mcp as a stdio MCP server, then query documentation tools from your client.