TaskPort MCP Agent Documentation

Connection

Connect over Streamable HTTP.

Use an agent access token created inside TaskPort. Never use your TaskPort password. Select Streamable HTTP (or HTTP) in your MCP client—not stdio or legacy SSE.

Common client configuration

{
  "mcpServers": {
    "taskport": {
      "url": "https://abafbnwpzdqxyhtrkdsg.supabase.co/functions/v1/taskport-mcp",
      "headers": {
        "Authorization": "Bearer tp_live_REPLACE_WITH_TOKEN",
        "Accept": "application/json, text/event-stream"
      }
    }
  }
}

Prefer your client’s secret or environment-variable reference instead of pasting the raw token into a configuration file.

Authentication

Get a token from TaskPort.

1. 1

   Open TaskPort → Settings → Manage Agent Access.

2. 2

   Choose New Agent, name it, and select a permission level.

3. 3

   Copy the one-time token beginning with tp_live_.

4. 4

   Add it to your MCP client and call list_lists to verify.

Access control

Choose exactly what an agent can do.

Write tools are not advertised to a read-only token. Each token belongs to exactly one user, and every operation verifies ownership.

Tool reference

Available MCP tools.

Files

Attachments and MCP.

TaskPort tasks can contain multiple images and files. Users add them from TaskPort on iPhone, iPad, or Mac, or by sharing a supported file to TaskPort from another app.

Upload a file from an agent

1. 1

   Call prepare_attachment_upload with the target task_id, exact file_name, mime_type, and raw byte_size. Keep the returned attachment.id, chunk_size, and chunk_count.

2. 2

   Split the raw file into blocks of at most 4,194,304 bytes. Base64-encode each block separately, then call upload_attachment_chunk for indexes 0 through chunk_count - 1. Do not send a data-URL prefix or split one already-encoded string.

3. 3

   Call complete_attachment_upload. TaskPort assembles the chunks, verifies their exact size, validates the actual file contents, stores the final object privately, and accounts for quota.

4. 4

   Use list_attachments or get_task to read its metadata. Call get_attachment_download_url only when the agent needs the bytes; the signed link expires after 60 seconds.

prepare_attachment_upload({
  "task_id": "TASK_UUID",
  "file_name": "brief.pdf",
  "mime_type": "application/pdf",
  "byte_size": 842119
})

upload_attachment_chunk({
  "attachment_id": "ATTACHMENT_UUID",
  "chunk_index": 0,
  "data_base64": "JVBERi0xLjcK..."
})

complete_attachment_upload({
  "attachment_id": "ATTACHMENT_UUID"
})

Chunk uploads are retry-safe: sending the same index again replaces that temporary chunk. If the workflow cannot finish, call cancel_attachment_upload to release the reservation immediately; otherwise it expires after two hours.

Executables, scripts, generic archives, SVG, encrypted documents, and Office files containing macros are rejected. TaskPort validates file content in addition to its filename and declared media type.

Dates and time zone

Use the user’s local calendar date.

Due dates are calendar dates in YYYY-MM-DD format, not timestamps. The server does not expose the user’s time zone. Determine “today” from the user’s profile or ask, then pass the matching local date.

Troubleshooting

Expected errors.

Still stuck? Visit TaskPort Support.