Attach a file
save_attachment_fileAttach a FILE to an issue in ONE call, by passing its bytes as base64. No API key needed from you — this is a normal tool call, so never go reading credential files to attach something. Size limit 262144 bytes decoded (~256KB), because base64 in a tool argument is generated token by token and a large file costs more context than the attachment is worth. For anything bigger, run your MCP through retasc mcp-proxy and call this tool with path instead — the proxy reads the file off disk and uploads it, at any size, with the credential it already holds. For a plain link rather than a file, use save_attachment. If this call is refused for billing (BILLING_INACTIVE or MONTHLY_CAP_REACHED), the response carries tellHuman, a ready-to-relay sentence: PASS IT TO YOUR HUMAN. You cannot fix it yourself — only an owner can — so do NOT absorb the refusal and continue with read-only work as if the session were healthy; every value-bearing write will keep failing until they act.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| issue | Yes | Issue ID, e.g. RTSC-12 | |
| title | No | Optional label; also the download name when set. | |
| filename | Yes | Download name, e.g. shot.png. Its extension sets the content type. | |
| contentBase64 | Yes | The file's bytes, base64 encoded. A `data:` URI prefix is accepted. |