Files
Per-user file storage: keep a file, get a URL, read it back
Calling it
This is your own data, so a call has to say who you are. Make a token at /token and send it as a header.
curl -H "Authorization: Bearer $MU_TOKEN" \ https://mu-mcp.yvangodard.me/api/v1/files/list
Methods
POST /api/v1/files/deleteDelete a file you own
| Argument | Type | Description |
|---|---|---|
id * | string | The file's id |
curl -X POST \
-H "Authorization: Bearer $MU_TOKEN" \
-H "Content-Type: application/json" \
-d '{"id":"id"}' \
https://mu-mcp.yvangodard.me/api/v1/files/deleteGET /api/v1/files/getRead a stored file back by its id
| Argument | Type | Description |
|---|---|---|
id * | string | The file's id, as returned by files_put or files_list |
curl \ -H "Authorization: Bearer $MU_TOKEN" \ "https://mu-mcp.yvangodard.me/api/v1/files/get?id=id"
GET /api/v1/files/listList the caller's stored files, newest first
curl \ -H "Authorization: Bearer $MU_TOKEN" \ "https://mu-mcp.yvangodard.me/api/v1/files/list"
POST /api/v1/files/putStore a file and get a URL for it — a report, a CSV, a transcript
| Argument | Type | Description |
|---|---|---|
name * | string | File name including its extension, e.g. "report.csv" |
content * | string | The file's contents — plain text, or base64 when encoding is "base64" |
encoding | string | "base64" for binary files; omit for text |
type | string | Optional content type, e.g. "text/csv". Guessed from the name when omitted |
curl -X POST \
-H "Authorization: Bearer $MU_TOKEN" \
-H "Content-Type: application/json" \
-d '{"content":"content","name":"name"}' \
https://mu-mcp.yvangodard.me/api/v1/files/putThe same methods are tools over MCP, and every service on this instance is in one reference. Same method, same answer, same price.


