Imagin.studio Api Docs

@IMAGIN-studio

About Imagin.studio Api Docs

No overview available yet

#mcp #documentation #rag #search #imagin #model-context-protocol

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "imagin-docs": {
      "command": "uvx",
      "args": [
        "imagin-studio-api-docs-mcp"
      ]
    }
  }
}

Tools

No tools detected

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Imagin.studio Api Docs?

The Imagin.studio Api Docs MCP server gives AI coding assistants instant access to the full IMAGIN.studio documentation — including CDN configuration, API references, and integration guides. It is designed for developers using any major AI coding assistant that supports the Model Context Protocol.

How to use Imagin.studio Api Docs?

Install the server via uvx imagin-studio-api-docs-mcp (preferred) or npx -y @imagin.studio/api-docs-mcp. Add the provided JSON to your agent’s MCP configuration file. On first run, the server clones the upstream documentation and builds a local vector index (approximately 30 seconds). Your AI assistant can then call the search_docs tool to find relevant documentation.

Key features of Imagin.studio Api Docs

Single command installation, no cloning or manual setup required
Works with every major AI coding assistant
Runs entirely locally – no API keys or external services needed
Index automatically updates when upstream documentation changes
Packages available on both PyPI and npm

Use cases of Imagin.studio Api Docs

Search IMAGIN.studio docs for CDN cache invalidation details
Look up how to set up a custom domain with IMAGIN
Find the API endpoint for image transformations
Check which image formats IMAGIN.studio supports
Retrieve integration guides without leaving the coding environment

FAQ from Imagin.studio Api Docs

What are the runtime requirements?

The server requires either uvx (part of the uv toolchain) or npx (Node.js package runner). No other dependencies or virtual environments are needed.

Does the server require an API key or external service?

No. Everything runs locally and no API keys or external services are used.

Where does the documentation data come from?

On first run, the server clones the public IMAGIN.studio documentation from docs.imagin.studio and builds a local vector index.

Does the documentation index stay up to date?

Yes, the index automatically updates whenever the upstream documentation changes.

Which AI coding assistants are supported?

The server supports Claude Code, Claude Desktop, Cursor, Windsurf, VS Code + Copilot, Cline, and Zed.

Frequently asked questions

What are the runtime requirements?

The server requires either `uvx` (part of the uv toolchain) or `npx` (Node.js package runner). No other dependencies or virtual environments are needed.

Does the server require an API key or external service?

No. Everything runs locally and no API keys or external services are used.

Where does the documentation data come from?

On first run, the server clones the public IMAGIN.studio documentation from `docs.imagin.studio` and builds a local vector index.

Does the documentation index stay up to date?

Yes, the index automatically updates whenever the upstream documentation changes.

Which AI coding assistants are supported?

The server supports Claude Code, Claude Desktop, Cursor, Windsurf, VS Code + Copilot, Cline, and Zed.

Comments

Basic information

More Memory & Knowledge MCP servers

Rust Docs MCP Server

Govcraft

🦀 Prevents outdated Rust code suggestions from AI assistants. This MCP server fetches current crate docs, uses embeddings/LLMs, and provides accurate context via a tool call.

286

OpenLore

aakarim

Serve your docs to AI agents over SSH and MCP. Agents use ls, cat, grep, find, and pipes against a virtual filesystem backed by your documentation. Identity-scoped access, governed writing with human approval, and portab