Imagin.studio Api Docs
@IMAGIN-studio
Imagin.studio Api Docs について
概要はまだありません
基本情報
設定
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"imagin-docs": {
"command": "uvx",
"args": [
"imagin-studio-api-docs-mcp"
]
}
}
}ツール
ツールは検出されませんでした
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
概要
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.
「メモリとナレッジ」の他のコンテンツ
Notion MCP Integration
danhilseA simple MCP integration that allows Claude to read and manage a personal Notion todo list
🧠 Ultimate MCP Server
DicklesworthstoneComprehensive MCP server exposing dozens of capabilities to AI agents: multi-provider LLM delegation, browser automation, document processing, vector ops, and cognitive memory systems
MCP server for Obsidian
MarkusPfundsteinMCP server that interacts with Obsidian via the Obsidian rest API community plugin
Ultimate Google Docs & Drive MCP Server
a-bonusThe Ultimate Google Docs, Sheets, Drive, Gmail, & Google Calendar MCP Server. This MCP (primarily for use in Claude Desktop) gains full access to your google suite and lets claude do its thing.
Jupyter Notebook MCP Server (for Cursor)
jbenoModel Context Protocol (MCP) server designed to allow AI agents within Cursor to interact with Jupyter Notebook (.ipynb) files
コメント