# DataSklad Tracker: task links, API and MCP

This is a private, self-hosted Kaneo task tracker. Its task short links use:

    https://tracker.datasklad.com/t/<taskId>

The final path segment is the actual immutable Kaneo task ID, not a separate
shortener key. It can be passed directly to the API or to MCP's get_task tool.
Task renames, status changes and project moves keep the same task ID.

In a browser the short link requires sign-in, checks access through the normal
task API and redirects to the task's current workspace/project page. Do not
depend on browser redirects or scrape the sign-in page to obtain task data.

## Authentication and project access

Use the developer's own API key or that project's technical account key:

    Authorization: Bearer <your-api-key>

A link identifies a task; it does not grant access. Keys retain their normal
workspace/project permissions. Never put keys into a shared URL. A 401 response
requires authentication; 403/404 means the task is unavailable to that account.

## API

API base: https://tracker.datasklad.com/api
OpenAPI contract: https://tracker.datasklad.com/api/openapi

Read a task:

    GET /api/task/<taskId>

The authenticated response includes id, projectId, workspaceId, title,
description, status and other task fields. Use those returned identifiers.

Prefer narrow updates, preserving all other fields:

    PUT /api/task/title/<taskId>        {"title":"Updated title"}
    PUT /api/task/description/<taskId>  {"description":"Markdown description"}
    PUT /api/task/status/<taskId>       {"status":"<native-column-slug>"}

Read valid project statuses before changing one:

    GET /api/column/<projectId>

The virtual backlog status is planned. The API checks permissions for mutations.

Create a task in an authorized project:

    POST /api/task/<projectId>
    {"title":"Task title","description":"Markdown description","priority":"no-priority","status":"planned"}

After an uncertain creation response, re-read the project's tasks before retrying
so you do not create a duplicate. For paginated task/label reads follow the
pagination fields described by OpenAPI. Resolve primary/additional tags through
the project's custom fields and assigned labels; do not guess their IDs.

## MCP

Streamable HTTP MCP endpoint: https://tracker.datasklad.com/api/mcp
HTTP MCP requires the account's Kaneo OAuth/session Bearer token, not an API key.
Use the client's normal OAuth connection flow and discover the server's tools.
For API-key-only access use REST, or the Kaneo stdio MCP client configured with
that API key. Do not treat an HTTP MCP 401 as a reason to widen project permissions.
For a /t/<taskId> link, call get_task with taskId equal to the last path segment.
The existing create_task/update_task tools operate under that account's rights.
Read their schemas before use; a link alone is not an authorization token.