About Imagin.studio Api Docs
Imagin.studio Api Docs is an MCP server for coding assistants that provides semantic search across IMAGIN.studio CDN, API, and integration documentation. It builds and updates its index locally without API keys or external services.
Key features
- 01Semantic search across IMAGIN docs
- 02Builds a local vector index
- 03Automatically updates the index
- 04No API keys required
Use cases
- 01Find CDN configuration guidance
- 02Look up API endpoints and parameters
- 03Search integration guides
MCP support
The MCP server exposes the `search_docs` tool to search IMAGIN.studio documentation. Its documentation index is built and updated locally.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
1Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| query | string | Yes | Natural language search query. Use specific technical terms rather than vague descriptions. Good: "CDN cache invalidation headers". Bad: "caching stuff". |
| top_k | integer | No | Number of results to return (1-20, default 5). Use 1-3 for focused lookups, 5 for general questions, 10-20 for broad research. |
Details
From the project READMEIMAGIN.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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.