Add attachment to TP card
add_attachmentAttach a file to a Targetprocess card by ID using a server-side file path or base64 content and filename for chat-uploaded images.
Instructions
Upload a file (e.g. a screenshot or mockup) as an attachment on a Targetprocess card (bug, user story, feature, etc.) by its ID. filePath is read from THIS MCP SERVER'S OWN filesystem, not the calling assistant's — it only works for a file already on this machine. For an image attached/pasted/uploaded directly in the chat, read its bytes yourself and pass fileContent (base64) + fileName instead; passing that attachment's sandboxed path as filePath will fail with "file not found".
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"cardId": "<cardId>"
},
"name": "add_attachment"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cardId | Yes | TP card ID to attach the file to, e.g. 145789 | |
| fileName | No | File name to use when uploading via fileContent, e.g. screenshot.png | |
| filePath | No | Absolute path to a file on this MCP server's own filesystem. Do not use this for a file that only exists in the calling assistant's sandbox (e.g. a chat-attached image) — use fileContent instead. | |
| fileContent | No | Base64-encoded file content; use together with fileName. This is the reliable option for an image that came from a chat attachment/upload rather than a path already on this machine. |