Repository navigation
MCP: upload images and files — things, places, brands, types — from a URL or inline #548
Description
What you're trying to do
Give things a picture through MCP. Example: about two dozen network devices and cameras were added over MCP in one go; each should get the manufacturer's product photo, and most share one (three switches of the same model, three cameras of the same model).
What gets in the way today
MCP has no way to add a photo or file. attach_link returns a link to the capture sheet, so a person has to open it and upload by hand — one upload per thing, even when ten things share the same picture. The REST API can do it (POST /api/v1/files, then POST /api/v1/attachments), but an MCP client has no access to that.
What you'd like
An MCP tool that adds a photo (or another file role: manual, receipt, …) to a thing or place, from either:
- a public
httpsURL that Kept fetches itself (size and content-type limits, no private or loopback addresses, redirects re-checked), or - inline base64 for clients that already hold the bytes.
Nice to have: attach one uploaded file to several things in one call, so a shared product photo is stored once. The tool sets the photo as the thing's cover when it has none yet, and returns the file id so later calls can reuse it.
Activity
strausmann commentedon Nov 13, 2026
Scope: this should cover every place Kept accepts an image or file, not only things — one upload tool (or one per target, sharing the same URL/base64 input and limits) for:
Same rules everywhere: a public
httpsURL fetched by Kept (size/content-type limits, no private or loopback targets, redirects re-checked) or inline base64; the response returns the file id so one upload (e.g. a manufacturer's product photo) can be attached to several targets.[-]MCP: add a photo or file to a thing, from a URL or inline[/-][+]MCP: upload images and files — things, places, brands, types — from a URL or inline[/+]