IMAGIN.Studio API Docs
Semantic-search IMAGIN.studio CDN and API integration docs from the agent while wiring vehicle imagery into your app.
Overview
io.github.IMAGINstudio/api-docs-mcp is a build-phase MCP server that semantically searches IMAGIN.studio API documentation for CDN, API, and integration guidance.
What is this MCP server?
- 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
- Server version 0.1.17
- Two packages: PyPI imagin-studio-api-docs-mcp and npm @imagin.studio/api-docs-mcp
- Transport type stdio
What problem does it solve?
Builders integrating IMAGIN.studio waste time hunting scattered doc pages and risk wrong CDN URLs or parameters when the agent guesses the API.
Who is it for?
Solo developers shipping automotive imagery, configurators, or dealer sites who 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 do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Documentation MCP servers are shelved under build integrations because solo builders add them while connecting a third-party API to their product. This server indexes IMAGIN.studio API documentation—including CDN, API, and integration guides—so agents answer integration questions during implementation, not during idea brainstorming alone.
How it compares
Vendor API documentation MCP, not a generic OpenAPI linter skill or a cloud deploy integration.
Common Questions / FAQ
Who is io.github.IMAGINstudio/api-docs-mcp for?
It is for builders 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.