ImageKit MCP preflight — pick the right MCP server
Routing guide for ImageKit's three MCP servers — DAM (media library search/upload/share), Admin (origins, URL endpoints, usage), DevTools (docs search, transformation URLs) — plus companion skills for search, upload, ACLs and AI tagging
- What
- Routing guide for ImageKit's three MCP servers — DAM (media library search/upload/share), Admin (origins, URL endpoints, usage), DevTools (docs search, transformation URLs) — plus companion skills for search, upload, ACLs and AI tagging
- Cost
- Free
- Needs
- an ImageKit account with MCP access — DAM and Admin servers each need a separate connection and sign-in (DevTools needs none); an MCP-capable agent to host the connections
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @imagekit-developer's MCP preflight skill: a routing guide to be read before any ImageKit MCP call. It maps jobs to the right one of ImageKit's three hosted MCP servers — DAM (`imagekit.io/mcp/dam`) for media library search, upload, organize, tag, share, metadata, collections, path policies, public links and cache purge; Admin for origins/external storage, URL endpoints, and account usage analytics; DevTools for docs search (`search_docs`) and transformation-URL building (`transformation_builder`) — with strict rules (DAM for the media library, Admin for origins/usage — never cross them; never inline file bytes, use signed upload; filter search on the server; search docs before writing integration code). Points to companion skills for search-assets (Lucene queries), upload-files, asset-access-control (file/folder vs collection ACLs), ai-tasks and imagekit-integrations. Honest caveats: DAM and Admin each need a separate connection and ImageKit sign-in (DevTools doesn't) — a missing tool means that server isn't connected or permissioned; the account's free/paid tier is not asserted here. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: an ImageKit account with MCP access — DAM and Admin servers each need a separate connection and sign-in (DevTools needs none); an MCP-capable agent to host the connections Install "ImageKit MCP preflight — pick the right MCP server" for me. It gives my agent @imagekit-developer's routing guide for ImageKit's three MCP servers: DAM (https://imagekit.io/mcp/dam) for media library search, upload, organize, tag, share, metadata, collections, path policies, public links and cache purge; Admin for origins/external storage, URL endpoints, account usage and usage analytics; DevTools for docs search and transformation-URL building — with rules (DAM for media library, Admin for origins/usage, never inline file bytes, filter search on the server, search docs before writing integration code) and pointers to companion skills (search-assets, upload-files, asset-access-control, ai-tasks, imagekit-integrations). MIT-licensed. Repository: https://github.com/imagekit-developer/skills/blob/main/skills/mcp-preflight/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mcp-preflight". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. connect my ImageKit MCP servers in my agent client and sign in — that's on me). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.