Niches · CMS & website publishing
Upload images and attach them to an entry
One company's docs show a full fit.
What counts as done
Asset stored with alt text, referenced from the named entry or field, rendered on the preview and the editor canvas, with dimensions recorded, without the file's bytes passing through the model's context.
Measured, for our own tests: in at most three calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: add these photos to the gallery page
, use this image as the featured image
, put the generated hero image on the page
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
Does the job, with a limit 14
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| BCMS F Becomes tech, LLC | request-upload-media-url returns an upload URL, but sending the bytes needs a shell or HTTP step outside MCP, and no alt-text or from-URL parameter is documented. source |
| ButterCMS D ButterCMS LLC | Media fields take {url, alt} and the file is copied into the Media Library server-side in the same write, but only behind the paid Write API, and dimensions aren't documented. source |
| Cosmic BB Cosmic Inc. | cosmic_media_upload takes a URL so bytes stay out of context and media reads give dimensions, but the MCP page doesn't show an alt-text parameter on upload. source |
| DatoCMS BB Dato Srl | uploads.createFromUrl takes a remote URL with default alt text and runs inside an MCP script, but acc-29 shows the Free plan's upload quota stopping uploads. source |
| Directus C Monospace Inc. (doing business as Directus) | The files tool's import action fetches a URL server-side, then the item references the file id; Directus files have title and description but no dedicated alt-text field. source |
| dotCMS C dotCMS LLC | upload_assets streams files from a local directory to the site and can publish and verify them, bytes staying out of context, but it needs local files, not a URL, and alt text isn't covered. source |
| Ghost C Ghost Foundation Ltd | The image endpoint takes a multipart file with a ref, not a remote URL, so an agent needs a shell to send bytes; alt text is set on the post, not on upload. source |
| Hygraph B Hygraph GmbH | createAsset with a remote URL through execute_graphql keeps bytes out of context, but the asset is pending until processed and alt text is a custom field, not built in. source |
| Payload D Payload CMS, Inc. | REST takes a multipart upload to the upload collection, so bytes go from disk, not context; over MCP every media create fails with MissingFile (acc-21). source |
| Prismic C Prismic.io Inc. | upload_asset fetches a URL server-side and returns the CDN URL, and image fields carry alt text; the docs don't say dimensions are recorded or that the result shows on the editor canvas. source |
| Storyblok B Storyblok GmbH | upload_asset returns a signed S3 URL and a cURL command, and the docs say finishing needs shell access, so web clients can't complete it. source |
| Strapi BB Strapi, Inc. | The MCP's media tools write metadata only (media_update_asset sets alternativeText); the file must go up through REST multipart, and no upload-from-URL is documented. source |
| Webflow BB Webflow, Inc. | create_asset returns a presigned target and the bytes must be POSTed, with alt text set by update_asset; acc-24 shows API-inserted images missing in the Designer and carrying no dimensions. source |
| WordPress B WordPress.org, an open-source project. The WordPress trademark belongs to the WordPress Foundation | POST /wp/v2/media takes the file bytes and alt_text, with media_details recording sizes, but there's no upload-from-URL, and acc-35 saw body images dropped silently by a cross-posting tool. source |
Doesn't do this job 3
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Contentstack B Contentstack Inc. | The MCP's 78 cma tools and the cma-extended group have no asset create or upload; only metadata updates and folders. source |
| CookieYes MCP Server D CookieYes Limited | No upload or asset tool in the tool table. source |
| Kontent.ai BB Kontent CZ s.r.o. | The MCP's asset tools are get, list and update only; upload needs the Management API's binary file endpoint outside MCP. source |
What stops agents finishing
- MCP server has no upload tool or no file parameter (Payload, Strapi)
- upload needs a presigned S3 step only shell access can do (Storyblok over MCP)
- base64-only upload forces bytes through context
- free-tier asset quota
Around it
Before: image-generation.create, file-storage.read. After: cms.draft-post, cms.create-page.
Where this comes from
Weight 14 of 100 in CMS & website publishing: 8 of 39 accounts (one not on a listing); lowered from 15 for that; upload is the step most often missing from an MCP server
The same as data: /api/v1/use-cases/cms.upload-media.json, or the MCP tool get_use_case with id cms.upload-media. Other jobs in this category: /api/v1/niches?category=cms.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.