IMAGIN.studio API Docs

io.github.IMAGINstudioPublished by GitHub account IMAGINstudiov0.1.17Updated Oct 24, 2026

Semantic search over IMAGIN.studio API documentation — CDN, API, integration guides, and more.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives an AI assistant semantic search over IMAGIN.studio API documentation, including CDN, API and integration guides.

What you can do
  • Search IMAGIN.studio documentation semantically through a single search_docs tool
  • Look up CDN configuration and cache invalidation details
  • Find API references such as image transformation endpoints and supported image formats
  • Retrieve integration and custom domain setup guides
When to use it
Useful when you are building against IMAGIN.studio's CDN or API and want the assistant to answer from the official docs instead of guessing. It is a narrow, single-purpose docs lookup server.
Requirements
Runs locally over stdio, launched with uvx (Python) or npx (Node.js). On first run it clones the docs repository and builds a local vector index, which takes about 30 seconds and needs network access; the index refreshes when upstream docs change. No API keys or accounts are declared.
Before you install
The first run downloads and clones the upstream documentation and builds a local index, so it needs network access and some disk space. The index auto-updates from upstream, so content can change without your action. It only reads documentation; no write actions are described.

Installation

In SourceWeft

  1. Open IMAGIN.studio API Docs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:

json
{  "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

  1. Install — uvx imagin-studio-api-docs-mcp (no cloning, no venv, no config)
  2. Index — On first run, clones the docs and builds a local vector index (~30 sec)
  3. Search — Your AI assistant calls search_docs to find relevant documentation
  4. Stay fresh — The index auto-updates when the upstream docs change

Everything runs locally. No API keys. No external services.

Supported Agents

AgentConfig location
Claude Code.mcp.json in project root
Claude Desktopclaude_desktop_config.json
CursorSettings > Tools & MCP
Windsurf~/.codeium/windsurf/mcp_config.json
VS Code + Copilot.vscode/mcp.json
ClineMCP 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):

json
{  "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

RegistryPackageInstall
PyPIimagin-studio-api-docs-mcpuvx imagin-studio-api-docs-mcp
npm@imagin.studio/api-docs-mcpnpx -y @imagin.studio/api-docs-mcp

License

Apache License 2.0 — see LICENSE.

Source: README.md at commit a82d346

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.17LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts