4,500+ servers built on MCP Fusion
Vinkius

imgix MCP. Control your image CDN without touching a dashboard.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

imgix (Real-time Image Processing) MCP on Cursor AI Code Editor MCP Client imgix (Real-time Image Processing) MCP on Claude Desktop App MCP Integration imgix (Real-time Image Processing) MCP on OpenAI Agents SDK MCP Compatible imgix (Real-time Image Processing) MCP on Visual Studio Code MCP Extension Client imgix (Real-time Image Processing) MCP on GitHub Copilot AI Agent MCP Integration imgix (Real-time Image Processing) MCP on Google Gemini AI MCP Integration imgix (Real-time Image Processing) MCP on Lovable AI Development MCP Client imgix (Real-time Image Processing) MCP on Mistral AI Agents MCP Compatible imgix (Real-time Image Processing) MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

imgix (Real-time Image Processing) MCP Server gives your AI agent full control over your image CDN. List, create, and manage sources (S3, GCS, Web Folder).

Purge assets globally and get metadata for any image path. This lets you control your entire image delivery pipeline from a chat interface.

What your AI agents can do

Create source

Links your origin storage (S3, GCS, web folder) to Imgix CDN, making it a new source.

Delete source

Permanently removes an existing Imgix source definition.

Disable source

Stops a source from serving images, effectively taking it offline.

+ 7 more capabilities included
Manage Image Sources

Connect, list, update, or delete entire sources, linking your original storage (S3, GCS, Web Folder) to the imgix CDN.

Purge CDN Cache

Remove an asset from the global imgix cache. This invalidates all processed versions and forces the network to re-fetch the original file.

Audit Asset Metadata

Get detailed information on specific files, including their path, size, and content type, directly from the origin source.

Control Source State

Enable or disable a source definition to instantly manage whether or not it serves images through the CDN.

List All Assets

Retrieve a list of all files and their metadata from a specific source, useful for inventory checks.

Modify Source Settings

Update source configurations, including caching attributes or deployment settings, without deep API calls.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

imgix MCP Server: 10 Tools for Image CDN Operations

Manage every aspect of your image delivery pipeline—from creating new sources to purging individual assets—using conversational commands.

create019d75b8

create source

Links your origin storage (S3, GCS, web folder) to Imgix CDN, making it a new source.

delete019d75b8

delete source

Permanently removes an existing Imgix source definition.

disable019d75b8

disable source

Stops a source from serving images, effectively taking it offline.

enable019d75b8

enable source

Restores a source to active status, allowing it to serve images again.

get019d75b8

get asset

Retrieves metadata for a single asset, including its path, size, and content type.

get019d75b8

get source

Gets detailed information on a specific source, including its domain and current status.

list019d75b8

list assets

Lists all files and their metadata within a specified source.

list019d75b8

list sources

Lists every source connected to your imgix account.

action019d75b8

purge

Removes a specific asset from the global imgix CDN cache, forcing a re-fetch of the original file.

update019d75b8

update source

Modifies the settings of an existing source, like caching rules or deployment type.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with imgix (Real-time Image Processing), then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

Your AI agent gives you full control over your image CDN. You'll manage your whole image delivery pipeline just by talking to your agent. You can connect, check, and fix everything without ever touching a dashboard.

Managing Image Sources

  • You can use list_sources to see every source connected to your imgix account. You'll use get_source to pull detailed info on a specific source, like its domain and current status. You can create_source to link your origin storage—whether it's S3, GCS, or a web folder—making it a new source. If you need to make changes, you'll update_source to modify settings like caching rules or deployment type. You'll use delete_source to permanently pull an existing source definition. You can also disable_source to stop a source from serving images, or enable_source to bring it back online.

How imgix MCP Works

  1. 1 Subscribe to the imgix MCP Server and provide your API Key.
  2. 2 Tell your agent the source or asset you want to manage (e.g., 'Purge this logo image').
  3. 3 The agent executes the necessary tool (like purge or get_source) and reports the status and outcome back to you.

The bottom line is: you manage your entire image CDN stack using natural conversation, treating infrastructure control like a simple chat command.

Who Is imgix MCP For?

The SRE who gets burned out clicking through dashboards at 2 am. The frontend developer who needs to confirm a source connection and purge assets without leaving their IDE. Or the Digital Asset Manager who needs to audit hundreds of assets across multiple projects. This tool lets you treat your CDN like a chat window.

DevOps Engineer

Manages source availability and deploys/disables CDN sources in a single conversation. Uses list_sources and disable_source to control traffic flow.

Frontend Developer

Verifies origin connections and purges processed image derivatives after updating assets. Uses create_source and purge to sync local changes globally.

Digital Asset Manager

Audits asset libraries and checks source details across different projects. Uses list_sources and get_source to maintain a complete asset inventory.

What Changes When You Connect

  • Purge images globally: Need to update a logo? Use the purge tool to invalidate a single asset across the entire imgix Edge network. No more waiting for cache expiry.
  • Audit your entire setup: Use list_sources to see every connected source in one go. Quickly check the status of all deployments before a major release.
  • Pinpoint asset data: Use get_asset to get metadata (size, content type) on a specific file path. This is faster than downloading and inspecting the file manually.
  • Manage traffic flow: If a source needs maintenance, use disable_source. This instantly stops serving images from that source, controlling deployment windows via chat.
  • Keep your code synced: After a build, use create_source or update_source to ensure your local development assets are correctly linked and deployed to the CDN.
  • Get a full inventory: Use list_assets to list every file in a specific source. This gives you a complete manifest of assets for auditing purposes.

Real-World Use Cases

01

Emergency Logo Update

The marketing team drops a new logo file. Instead of waiting for the cache to expire, they ask their agent to purge the old asset URL. The agent sends the purge request, and the new logo loads immediately, solving the problem in seconds.

02

Pre-Deployment Check

A DevOps engineer is ready to deploy a new product line. They run list_sources to confirm all necessary sources are active, then use get_source to check the detailed deployment status of the main e-commerce source before flipping the switch.

03

Debugging Broken Assets

The frontend developer finds a broken image. They use get_asset to check the file's actual metadata, confirming if the source is correct and if the asset exists. They then use list_assets to check the surrounding files for context.

04

Shutting Down Old Sources

An old, unused marketing campaign source is taking up resources. The Digital Asset Manager uses disable_source to take it offline immediately. Later, they use delete_source when it's confirmed that the source is no longer needed.

The Tradeoffs

Guessing the state

Trying to remember if a source is live, disabled, or if an asset was purged correctly by checking the dashboard status manually.

Always confirm the state first. Run get_source to verify the current status, and if you need to force an update, use purge rather than just hoping the cache clears.

Missing the audit trail

Running a complex deployment involving multiple asset changes and then having no record of what was actually updated or which assets were affected.

Always run list_assets on the source before and after the changes. This gives you a clear, auditable manifest of everything that changed.

Over-relying on deletion

Assuming that deleting a source definition (delete_source) also cleans up all associated cached assets or metadata, which it might not.

Use disable_source first to stop traffic flow. Then, if it’s truly done, use delete_source. This ensures a controlled, reversible process.

When It Fits, When It Doesn't

Use this if you need to treat your CDN infrastructure like a set of chat commands. You need to audit, enable, disable, or purge assets based on natural language conversation.

Don't use this if your only goal is to view a simple list of all assets (use a dedicated asset management tool) or if you need to perform highly complex, proprietary data transformations that aren't exposed via imgix's API. For deep data manipulation, you still need to connect to the underlying storage (S3, GCS).

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by imgix. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

create_source delete_source disable_source enable_source get_asset get_source list_assets list_sources purge update_source

Checking CDN status means clicking through five different dashboards.

Right now, managing a source connection means opening the imgix dashboard, navigating to 'Sources,' finding the right domain, and then checking deployment status. If you need to list assets, you jump to another tab, and if you need to purge, you run a separate command line. It's a disjointed, multi-click process.

With the imgix MCP Server, you just talk to your agent. You tell it, 'List all my sources,' and you get the status immediately. You tell it, 'Purge the logo,' and the action happens. It turns a multi-dashboard workflow into a single chat command.

imgix (Real-time Image Processing) MCP Server: Get control over assets.

You don't have to manually update caching attributes or manually check if a source is active. The agent handles the logic. You can ask it to `update_source` or `enable_source` and confirm the state change immediately.

The difference is control. You manage the entire asset lifecycle—from initial connection (`create_source`) to final deletion (`delete_source`)—without ever leaving your IDE or chat window.

Common Questions About imgix MCP

How do I purge a specific asset using the purge tool? +

You provide the asset URL or path to the agent. The agent executes the purge tool, which invalidates the asset across the global imgix network immediately.

What is the difference between delete_source and disable_source? +

disable_source stops the source from serving images immediately. delete_source permanently removes the source definition. Always disable first if you aren't sure you never need it.

Can I list all assets in a source using list_assets? +

Yes, list_assets gathers all file paths, sizes, and content types from the source. It's a quick way to audit your asset inventory.

Do I need to run get_source before I can update_source? +

While you can run update_source directly, using get_source first helps you gather all the existing configuration parameters, making sure you don't miss anything when making changes.

Does create_source automatically handle the API key? +

No. You must subscribe to the server and provide your imgix API Key first. The tools only work once the connection is established.

What information does `get_source` return about an Imgix source? +

It returns the source's name, domain, deployment type, and current status. This lets you verify if a source is active, what domain it uses, and how it's set up for deployment.

If I run `list_sources` and see a source I don't need, how do I remove it? +

You use the delete_source tool. This permanently removes the source configuration. Make sure you've backed up any necessary details before deleting it.

How can I check the metadata for a single file using `get_asset`? +

The get_asset tool retrieves the asset's path, size, and content type. This is useful for knowing the file details before processing or displaying it.

What happens when I purge an asset in imgix? +

Using the purge tool removes the cached version of the original image and ALL processed derivatives (resized, filtered, etc.) from imgix Edge nodes. This forces the system to re-fetch the file from your origin storage on the next request.

Can I connect my AWS S3 bucket to imgix using my agent? +

Absolutely. Use the create_source tool and provide your S3 origin base URL. Your agent will handle the backend orchestration to map your storage bucket to a new imgix CDN domain.

How do I check if a source is currently serving traffic? +

The get_source tool retrieves the real-time status of any imgix source. Your agent will return the deployment type and current state, so you'll know exactly if it's enabled and live.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for imgix. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.