_ registry / mcp http-sse · checked 16h ago

tasklite

https://mcp.tasklite.net

Registry code: 6f84e86c916a4953

api record

TaskLite is the backend: data lives in boards (tables) inside projects

(one project = one business process). The boards are also the ready-made

endpoint
https://mcp.tasklite.net/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
115ms

last good check

priced tools
0

of 48 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 48 tools
1 auth-required 47 never probed 1 of 48 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_apps auth-required 16h ago

    List the apps in the organization, id, slug, status. Call this first when you need an app id: the slug (app-xxxxxx) is what shows up in URLs and in generated code, and this is how you map it back to the app.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • get_app_spec unknown never probed

    Get the machine-readable spec of an app: base URL, endpoints, methods, fields, auth. Two formats: "tasklite" (default), the compact shape the frontend prompts are built from, and "openapi", a standard OpenAPI 3.1 document for developers and other tools. When the user asks for the OpenAPI spec, or wants to hand the API to a developer, pass format "openapi". appId accepts either the app UUID or its slug (app-xxxxxx); list_apps shows both. The returned baseUrl is absolute, use it verbatim, do not rebuild it from the admin URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "format": {
      "enum": [
        "tasklite",
        "openapi"
      ],
      "type": "string",
      "description": "\"tasklite\" (default): compact endpoint list. \"openapi\": OpenAPI 3.1 document, every endpoint with typed fields, filter grammar, auth and errors"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • configure_external_access unknown never probed

    Read or change how EXTERNAL users (people who sign up to your app through TaskLite auth) get into an organization. They have two ways in, and both obey the policy below: email and password (POST /auth/register-external with this organizationId, then POST /auth/login), or Google (POST /auth/google-external with a Google ID token and this organizationId). Either way the answer carries a token the app sends as Authorization: Bearer on every App API call. registrationPolicy: "open", in at once; "approval", an organization admin approves each signup (TaskLite mails the admins on every signup, and the person once approved; unapproved users are never billed); "closed", invite only, self-signup refused. appLoginUrl: the page of YOUR app where these users log in, it becomes the "Log in" button in the approval email, so set it whenever you deploy an app that uses this flow; pass "" to clear. Call with no changes to just read the current settings. Requires organization admin.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "appLoginUrl": {
      "type": "string",
      "description": "https URL of your app's login page for external users; \"\" clears it"
    },
    "organizationId": {
      "type": "string",
      "description": "Defaults to the credential organization"
    },
    "registrationPolicy": {
      "enum": [
        "closed",
        "approval",
        "open"
      ],
      "type": "string",
      "description": "How external sign-ups are admitted: open, approval or closed"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • list_projects unknown never probed

    List projects in an organization. The API returns 50 per page, an organization with more than that needs page 2 and beyond, so check the returned total before assuming a project does not exist.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "page": {
      "type": "number",
      "description": "1-based; defaults to 1"
    },
    "limit": {
      "type": "number",
      "description": "Defaults to 50"
    },
    "organizationId": {
      "type": "string",
      "description": "Defaults to the credential organization"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • list_boards unknown never probed

    List the boards inside a project, id, name, description. Every other board tool needs a boardId, and this is the only way to discover one without being handed a URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId"
  ],
  "properties": {
    "page": {
      "type": "number",
      "description": "1-based; defaults to 1"
    },
    "limit": {
      "type": "number",
      "description": "Defaults to 50"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • create_project unknown never probed

    Create a project (a business process container). Boards with data live inside projects.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "description": {
      "type": "string",
      "description": "Free-text description"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • create_board unknown never probed

    Create a board (a data table) inside a project. Add typed columns with create_column afterwards. kind: "tasks" (default) also gives the board the built-in task columns, status, priority, assignee, due date, tags, for work people track; "data" creates a plain table with only the columns you add, for records such as customers, products or orders (requires a TaskLite server from 2026-09-06; older servers ignore kind).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "name"
  ],
  "properties": {
    "kind": {
      "enum": [
        "tasks",
        "data"
      ],
      "type": "string",
      "description": "\"tasks\": with the built-in task columns (status, priority, assignee, due date, tags). \"data\": only the columns you add. Default tasks."
    },
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "description": {
      "type": "string",
      "description": "Free-text description"
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • create_column unknown never probed

    Add a typed column to a board. Valid types: text, rich_text, number, status, date, datetime, duration, people, checkbox, dropdown, label, priority, link, email, phone, relation, lookup, rollup, formula, rating, currency, file. Choose by meaning, date for dates, phone for phones, number/currency for amounts, dropdown/status (with settings.options as an array of labels) for closed choices; text is for free text only. An obvious name/type mismatch is rejected with the suggested type; pass force:true to override. Rules go in settings.validation: { unique, min, max, minLength, maxLength, pattern, patternMessage }, enforced on every write (UI, MCP, App API). Closed choices (dropdown/status) reject values outside settings.options unless settings.allowCustom is true.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "name",
    "type"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "type": {
      "type": "string",
      "description": "Action type: http_request, send_notification, send_email, send_whatsapp, change_status, set_column_value, create_cross_board_item, send_webhook or delay"
    },
    "force": {
      "type": "boolean",
      "description": "Create the column even when the name suggests a different type"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "settings": {
      "type": "object",
      "description": "Type-specific settings. For dropdown/status/priority: options, either as labels [\"A\",\"B\"] or as full objects [{value,label,color}], labels are expanded server-side, and colors are assigned if you do not supply them.",
      "additionalProperties": {}
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "isRequired": {
      "type": "boolean",
      "description": "Require a non-blank value on every App API create"
    }
  },
  "additionalProperties": false
}
    arguments 42 lines
  • get_board_schema unknown never probed

    Get a board with its full column schema (ids, names, types, settings). Call this before creating items with cells.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId"
  ],
  "properties": {
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • update_board unknown never probed

    Rename a board or change its description. Structure (columns) is changed with update_column / delete_column / reorder_columns.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "description": {
      "type": "string",
      "description": "Free-text description"
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • delete_board unknown never probed

    Delete a board with every item on it. Destructive and not undoable, confirm with the user first, and prefer delete_column when only part of the model is wrong.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId"
  ],
  "properties": {
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • delete_project unknown never probed

    Delete a project with every board, column and row inside it. Destructive: confirm with the user first, and name the project in the confirmation. The project goes to the organization recycle bin, so it can be restored from the admin until it is emptied.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId"
  ],
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • update_column unknown never probed

    Change a column after the fact: rename it, change its type (e.g. number -> currency), replace settings (dropdown options), or set isRequired / isHidden. A type change converts existing values (number↔currency, text→number/date/checkbox, anything→text) and clears the ones that cannot convert; the response carries conversion: { converted, cleared }. settings.validation rules apply here too.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "columnId"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "type": {
      "type": "string",
      "description": "New column type (same list as create_column)"
    },
    "force": {
      "type": "boolean",
      "description": "Skip the name/type sanity check"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "columnId": {
      "type": "string",
      "description": "Column id (from get_board_schema)"
    },
    "isHidden": {
      "type": "boolean",
      "description": "Hide the column in the TaskLite UI"
    },
    "settings": {
      "type": "object",
      "description": "Replaces the column settings, e.g. { options: [...] } for dropdown/status",
      "additionalProperties": {}
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "isRequired": {
      "type": "boolean",
      "description": "Require a non-blank value on every App API create"
    },
    "description": {
      "type": "string",
      "description": "Free-text description"
    }
  },
  "additionalProperties": false
}
    arguments 53 lines
  • delete_column unknown never probed

    Delete a column and every value stored in it. Destructive, confirm with the user first. Use update_column when the column is right but its name, type or options are wrong.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "columnId"
  ],
  "properties": {
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "columnId": {
      "type": "string",
      "description": "Column id (from get_board_schema)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • reorder_columns unknown never probed

    Set the display order of a board's columns. Pass every column id in the wanted order (get_board_schema lists them).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "columnIds"
  ],
  "properties": {
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "columnIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Column ids in the new order (every column of the board)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • export_project unknown never probed

    The whole project as JSON, boards, columns with settings, items with their cells keyed by column id. For migrations, backups and reading a system back. Items are capped per board for the model's sake; the REST endpoint GET /organizations/{orgId}/projects/{projectId}/export.json returns everything.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId"
  ],
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "organizationId": {
      "type": "string",
      "description": "Defaults to the credential organization"
    },
    "maxItemsPerBoard": {
      "type": "integer",
      "maximum": 2000,
      "description": "Default 200",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • query_items unknown never probed

    List items (rows) of a board, including their cell values. Returns all items unless limit/page are given (the API defaults to 50 per page when unpaged, so the tool pages through and concatenates). Narrow the result with search, status, priority and sort instead of fetching everything. This is the admin view; the REST endpoints of a published app take a fuller grammar, filter[column][gte], relation filters, per-field search, see get_app_spec.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "description": "1-based page, only with limit",
      "exclusiveMinimum": 0
    },
    "sort": {
      "type": "string",
      "description": "Sort by title, createdAt, updatedAt or status; prefix with \"-\" for descending, e.g. \"-createdAt\" for newest first. Anything else keeps the board order"
    },
    "limit": {
      "type": "integer",
      "maximum": 500,
      "description": "Page size; omit to fetch all items",
      "exclusiveMinimum": 0
    },
    "search": {
      "type": "string",
      "description": "Free text; matches the row title and its text cells"
    },
    "status": {
      "type": "string",
      "description": "Only rows whose status is one of these, comma separated. Matched against the board's status column by option value or label, case-insensitive: \"todo,in_progress\" on a task board, \"Received,In Repair\" on a data board whose status column lists those (get_board_schema shows the options)"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "archived": {
      "enum": [
        "active",
        "archived",
        "all"
      ],
      "type": "string",
      "description": "Which rows to include. Default active"
    },
    "priority": {
      "type": "string",
      "description": "Only rows with one of these priorities, comma separated (task boards only)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "excludeStatus": {
      "type": "string",
      "description": "Only rows whose status is NOT one of these, comma separated, resolved like status. The way to ask for everything that is not done: excludeStatus \"done\" (task board) or \"Completed\" (a data board with that option). Rows with no status at all are kept"
    }
  },
  "additionalProperties": false
}
    arguments 59 lines
  • create_item unknown never probed

    Create an item (row) with all of its data in one call. cells maps columnId -> value (use get_board_schema for column ids); every cell is saved with the row. Use set_cell only for later edits.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "title"
  ],
  "properties": {
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags as an array of strings"
    },
    "cells": {
      "type": "object",
      "description": "Cell values keyed by column id: { \"<columnId>\": value }. Scalars, { amount, currency } for currency, { relatedItemIds: [...] } for relations",
      "additionalProperties": {}
    },
    "title": {
      "type": "string",
      "description": "Item title, shown as the row name"
    },
    "status": {
      "type": "string",
      "description": "Status value (todo, in_progress, done, or a value from the board's status options)"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "dueDate": {
      "type": "string",
      "description": "ISO date"
    },
    "priority": {
      "type": "string",
      "description": "Priority: low, medium, high or urgent"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "description": {
      "type": "string",
      "description": "Free-text description"
    }
  },
  "additionalProperties": false
}
    arguments 52 lines
  • update_item unknown never probed

    Update item fields (title, description, status, priority, dueDate, tags).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "itemId"
  ],
  "properties": {
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags as an array of strings"
    },
    "title": {
      "type": "string",
      "description": "Item title, shown as the row name"
    },
    "itemId": {
      "type": "string",
      "description": "Item (row) id"
    },
    "status": {
      "type": "string",
      "description": "Status value (todo, in_progress, done, or a value from the board's status options)"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "dueDate": {
      "type": "string",
      "description": "Due date, ISO 8601 (YYYY-MM-DD or full timestamp)"
    },
    "priority": {
      "type": "string",
      "description": "Priority: low, medium, high or urgent"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "description": {
      "type": "string",
      "description": "Free-text description"
    }
  },
  "additionalProperties": false
}
    arguments 51 lines
  • set_cell unknown never probed

    Set a single cell value on an item by columnId.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "itemId",
    "columnId",
    "value"
  ],
  "properties": {
    "value": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "number"
        },
        {
          "type": "boolean"
        },
        {
          "type": "null"
        },
        {
          "type": "array",
          "items": {}
        },
        {
          "type": "object",
          "additionalProperties": {}
        }
      ],
      "description": "The new cell value; shape depends on the column type"
    },
    "itemId": {
      "type": "string",
      "description": "Item (row) id"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "columnId": {
      "type": "string",
      "description": "Column id (from get_board_schema)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 55 lines
  • delete_item unknown never probed

    Delete an item. Destructive, confirm with the user before calling.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "itemId"
  ],
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item id (from query_items / create_item)"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • list_comments unknown never probed

    List the comments (the correspondence thread) on an item, oldest first. Each comment includes its author and any @mentions. Needs projectId and itemId (get itemId from query_items).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "itemId"
  ],
  "properties": {
    "page": {
      "type": "integer",
      "description": "1-based page, default 1",
      "exclusiveMinimum": 0
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "description": "Page size, default 20",
      "exclusiveMinimum": 0
    },
    "itemId": {
      "type": "string",
      "description": "Item (row) id"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • add_comment unknown never probed

    Post a comment on an item's thread. To notify people, pass their user ids in mentionedUserIds (each also appears as an @mention). attachmentIds references already-uploaded files. Needs projectId and itemId.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "itemId",
    "content"
  ],
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item (row) id"
    },
    "content": {
      "type": "string",
      "description": "The comment text"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "attachmentIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ids of already-uploaded attachments to link"
    },
    "mentionedUserIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "User ids to @mention and notify"
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
  • update_comment unknown never probed

    Edit the text of an existing comment. Only the author can edit their comment. Needs projectId, itemId and the commentId.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "itemId",
    "commentId",
    "content"
  ],
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item (row) id"
    },
    "content": {
      "type": "string",
      "description": "The new comment text"
    },
    "commentId": {
      "type": "string",
      "description": "Comment id (from list_comments)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • delete_comment unknown never probed

    Delete a comment from an item thread. Destructive, confirm with the user before calling. Needs projectId, itemId and the commentId.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "itemId",
    "commentId"
  ],
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item id (from query_items / create_item)"
    },
    "commentId": {
      "type": "string",
      "description": "Comment id (from list_comments / add_comment)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • request_file_upload unknown never probed

    Create a link that puts files onto an item from outside TaskLite: the customer's photos, a signed contract, a logo, a build zip. Returns an address like https://app.tasklite.net/upload/<token> that anyone you hand it to can use with no account, no login and no API key; pass clientEmail and TaskLite emails the link for you. What arrives lands as attachments on that item, and list_uploaded_files reads them back with a download URL. This is the answer when the person has the file and the model does not: a hosted client cannot read a folder on someone's machine. The link is public for as long as it lasts, so keep expiryDays short and maxFiles tight, and revoke_upload_link when the material is in.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "itemId"
  ],
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item (row) the files belong to, from query_items / create_item. Make the row first if the material has no home yet"
    },
    "message": {
      "type": "string",
      "description": "What to upload, in the words the recipient will read: \"the four room photos and the price list\""
    },
    "maxFiles": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "How many files the link accepts before it stops. Default 10"
    },
    "clientName": {
      "type": "string",
      "description": "Who is being asked, shown on the upload page"
    },
    "expiryDays": {
      "type": "integer",
      "maximum": 90,
      "minimum": 1,
      "description": "How long the link lives. Default 7 days"
    },
    "clientEmail": {
      "type": "string",
      "format": "email",
      "description": "Send the link to this address. Omit to get the link back and pass it on yourself"
    },
    "clientPhone": {
      "type": "string",
      "description": "Recorded with the request"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 47 lines
  • list_uploaded_files unknown never probed

    The files attached to an item, including everything that came in through a request_file_upload link, each with a download URL that is signed and short lived (mint a fresh one by calling again). Also lists the upload links on the item and how many files each has taken, which is how to tell whether the person you asked has delivered.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "itemId"
  ],
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item (row) id"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • revoke_upload_link unknown never probed

    Close an upload link before it expires, so the address stops accepting files. The files already uploaded stay on the item. Use it as soon as the material is in, because until then anyone holding the link can add more.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "tokenId"
  ],
  "properties": {
    "tokenId": {
      "type": "string",
      "description": "Link id (the tokenId from request_file_upload)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • push_status unknown never probed

    Whether an app can send push notifications to phones, and how many devices are registered. Push goes out through the customer's OWN Firebase project, so it has to be configured once per app before send_push automations do anything. This tool never returns the key.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • send_test_push unknown never probed

    Send one real push notification to the given app users, to prove the chain works before an automation depends on it. Confirm with the user first: this reaches actual phones.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "userIds"
  ],
  "properties": {
    "body": {
      "type": "string",
      "description": "Notification body"
    },
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "title": {
      "type": "string",
      "description": "Notification title; defaults to \"TaskLite\""
    },
    "userIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "App user ids to notify (the same ids row-level security uses)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • create_app_endpoint unknown never probed

    Expose a board as a REST endpoint of an app: /apps/{appSlug}/api/{slug}. exposedColumns limits which columns are readable/writable. rowLevelSecurity.enabled makes the endpoint per-user: the developer's server sends `X-App-User: <their user id>` next to the API key, and the endpoint returns, updates and deletes ONLY that user's rows (401 without the header). Use it whenever the app has its own users.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "boardId",
    "slug",
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "slug": {
      "type": "string",
      "description": "URL slug: lowercase letters, digits and dashes"
    },
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "allowedMethods": {
      "type": "array",
      "items": {
        "enum": [
          "GET",
          "POST",
          "PATCH",
          "DELETE"
        ],
        "type": "string"
      },
      "description": "HTTP methods the endpoint accepts: GET, POST, PATCH, DELETE"
    },
    "exposedColumns": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "columnId"
        ],
        "properties": {
          "alias": {
            "type": "string",
            "description": "JSON key exposed for this column: letters, digits, underscore. Never one of the reserved item fields id, title, description, status, priority, dueDate, assignedTo, createdAt, updatedAt, order, appUserId, a business status column becomes repairStatus or orderStatus, not status."
          },
          "columnId": {
            "type": "string",
            "description": "Column id (from get_board_schema)"
          },
          "readOnly": {
            "type": "boolean",
            "description": "Expose the column for reading only; writes to it are refused with 400"
          }
        },
        "additionalProperties": false
      },
      "description": "Columns the endpoint reads and writes, with the JSON key each one gets; without it the endpoint returns bare metadata"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    },
    "rowLevelSecurity": {
      "type": "object",
      "required": [
        "enabled"
      ],
      "properties": {
        "mode": {
          "enum": [
            "owner",
            "shared",
            "phone"
          ],
          "type": "string",
          "description": "\"owner\" (default): each user sees and edits only the rows they created. \"shared\": every user authorized on the app (listed on it, or an owner/admin of the organization) sees and edits every row; the mode for an admin screen or a team system. \"phone\": a user signed in with a code sent to their phone sees and edits only the rows whose phoneColumn holds that phone, e.g. a directory where each person keeps their own card"
        },
        "enabled": {
          "type": "boolean",
          "description": "true: every request must carry a signed-in user (the token from sign-in, or the app key with X-App-User)"
        },
        "phoneColumn": {
          "type": "string",
          "description": "mode \"phone\" only: id of the column that holds each row's phone number (get_board_schema)"
        }
      },
      "description": "Row-level security. Off: whoever holds the app key reads everything. On: every request must name a signed-in user, and mode decides which rows they reach",
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}
    arguments 98 lines
  • list_app_endpoints unknown never probed

    List an app's REST endpoints, slug, board, allowed methods, and how many columns each exposes. An endpoint exposing 0 columns is broken: it returns only item metadata and silently discards writes.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • update_app_endpoint unknown never probed

    Change an existing endpoint, most often to set exposedColumns on one that was created without them. Get the endpoint id from list_app_endpoints and the column ids from get_board_schema.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "endpointId"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "slug": {
      "type": "string",
      "description": "URL slug: lowercase letters, digits and dashes"
    },
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "isActive": {
      "type": "boolean",
      "description": "Whether it is active"
    },
    "endpointId": {
      "type": "string",
      "description": "Endpoint id (from list_app_endpoints)"
    },
    "allowedMethods": {
      "type": "array",
      "items": {
        "enum": [
          "GET",
          "POST",
          "PATCH",
          "DELETE"
        ],
        "type": "string"
      },
      "description": "HTTP methods the endpoint accepts: GET, POST, PATCH, DELETE"
    },
    "exposedColumns": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "columnId"
        ],
        "properties": {
          "alias": {
            "type": "string",
            "description": "JSON key exposed for this column: letters, digits, underscore. Never one of the reserved item fields id, title, description, status, priority, dueDate, assignedTo, createdAt, updatedAt, order, appUserId, a business status column becomes repairStatus or orderStatus, not status."
          },
          "columnId": {
            "type": "string",
            "description": "Column id (from get_board_schema)"
          },
          "readOnly": {
            "type": "boolean",
            "description": "Expose the column for reading only; writes to it are refused with 400"
          }
        },
        "additionalProperties": false
      },
      "description": "Replacement list of exposed columns (same shape as create_app_endpoint)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    },
    "rowLevelSecurity": {
      "anyOf": [
        {
          "type": "object",
          "required": [
            "enabled"
          ],
          "properties": {
            "mode": {
              "enum": [
                "owner",
                "shared",
                "phone"
              ],
              "type": "string",
              "description": "\"owner\" (default): each user sees and edits only the rows they created. \"shared\": every user authorized on the app (listed on it, or an owner/admin of the organization) sees and edits every row; the mode for an admin screen or a team system. \"phone\": a user signed in with a code sent to their phone sees and edits only the rows whose phoneColumn holds that phone, e.g. a directory where each person keeps their own card"
            },
            "enabled": {
              "type": "boolean",
              "description": "true: every request must carry a signed-in user (the token from sign-in, or the app key with X-App-User)"
            },
            "phoneColumn": {
              "type": "string",
              "description": "mode \"phone\" only: id of the column that holds each row's phone number (get_board_schema)"
            }
          },
          "additionalProperties": false
        },
        {
          "type": "null"
        }
      ],
      "description": "Replacement row-level security (same shape as create_app_endpoint); null turns it off"
    }
  },
  "additionalProperties": false
}
    arguments 107 lines
  • create_app_api_key unknown never probed

    Create an API key for an app. SECURITY: the key must live server-side only (env var, Next.js API routes), never in browser code. If the app has its own users, the server also sends `X-App-User: <user id>` with the key so per-user endpoints know who is acting.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "scopes": {
      "type": "array",
      "items": {
        "enum": [
          "read",
          "write"
        ],
        "type": "string"
      },
      "description": "Permissions recorded on the key: [\"read\"] or [\"read\",\"write\"]. Omit to match the app: write when any endpoint accepts POST, PATCH or DELETE."
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • build_backend unknown never probed

    Build a whole backend in one call from a spec you compose: the project, its boards, their typed columns (including relations between the boards), optional sample rows, and optionally a published REST API with one endpoint per board and a server-side key. Use it whenever the user describes a system ("a backend for my repair shop: customers, orders, payments") instead of calling create_project, create_board, create_column, create_app, publish_app, create_app_endpoint and create_app_api_key one by one. You do the design, pick column types by meaning (phone, date, currency, dropdown/status with options for closed choices), link boards with a relation column (type "relation", relatedBoard: "<board name in this spec>", relationType: many_to_one for an order→customer link), and this tool executes it and returns one compact summary. API field names are derived from column names and never collide with reserved item fields, so there is nothing to retry. Boards are created as plain data tables (kind "data": only the columns you define, no task fields); set kind "tasks" on a board where people track work to do and want status, priority, assignee and due date built in. Every row still has a title.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "project",
    "boards"
  ],
  "properties": {
    "api": {
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "App name; defaults to \"<project> API\""
        },
        "methods": {
          "type": "array",
          "items": {
            "enum": [
              "GET",
              "POST",
              "PATCH",
              "DELETE"
            ],
            "type": "string"
          },
          "description": "HTTP methods every endpoint accepts; defaults to all four"
        },
        "rowLevelSecurity": {
          "type": "boolean",
          "description": "true when the app has its own users and each may see only their rows (the caller then sends X-App-User)"
        }
      },
      "description": "Include to publish a REST API over every board and mint a key; omit for a boards-only build",
      "additionalProperties": false
    },
    "boards": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "columns"
        ],
        "properties": {
          "kind": {
            "enum": [
              "tasks",
              "data"
            ],
            "type": "string",
            "description": "\"data\" (default here): a plain table with only the columns you define, right for customers, products, orders, payments. \"tasks\": also the built-in task columns (status, priority, assignee, due date, tags), only for boards where people track work to do."
          },
          "name": {
            "type": "string",
            "description": "Board (table) name, e.g. \"Repair Orders\""
          },
          "rows": {
            "type": "array",
            "items": {
              "type": "object",
              "additionalProperties": {}
            },
            "description": "Optional sample rows keyed by column name, e.g. [{ \"Customer\": \"Sam Miller\", \"Phone\": \"052-555-0142\", \"Price\": 80 }]. \"title\" sets the row title; without it the first plain text value is used, and failing that the row is named after its board and position. A row that other boards reference must carry a title (or a text value) so the reference can be resolved. A relation cell takes the title(s) of rows in the related board (any order in the spec; rows are created in dependency order)."
          },
          "columns": {
            "type": "array",
            "items": {
              "type": "object",
              "required": [
                "name",
                "type"
              ],
              "properties": {
                "name": {
                  "type": "string",
                  "description": "Column name as the user would say it, e.g. \"Customer\", \"Phone\", \"Repair Status\""
                },
                "type": {
                  "type": "string",
                  "description": "text, rich_text, number, currency, date, datetime, phone, email, link, checkbox, dropdown, status, priority, rating, file, people, relation, label, duration"
                },
                "alias": {
                  "type": "string",
                  "description": "API field name to use instead of the derived one (letters, digits, underscore; not a reserved item field)"
                },
                "options": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  },
                  "description": "The closed choices for dropdown/status/priority, e.g. [\"Received\",\"In Repair\",\"Ready\",\"Completed\"]"
                },
                "required": {
                  "type": "boolean",
                  "description": "Reject API creates that leave it blank"
                },
                "settings": {
                  "type": "object",
                  "description": "Other type settings, e.g. { currency: \"ILS\" }. (relatedBoardName / relationType are also accepted here for compatibility.)",
                  "additionalProperties": {}
                },
                "validation": {
                  "type": "object",
                  "description": "{ unique, min, max, minLength, maxLength, pattern, patternMessage }",
                  "additionalProperties": {}
                },
                "relatedBoard": {
                  "type": "string",
                  "description": "relation columns only: the name of another board in this spec that this column links to, e.g. \"Customers\""
                },
                "relationType": {
                  "enum": [
                    "many_to_one",
                    "one_to_many",
                    "many_to_many",
                    "one_to_one"
                  ],
                  "type": "string",
                  "description": "relation columns only. many_to_one: many rows here point at one row there (an order has one customer; a payment has one order). one_to_many: one row here owns many there. many_to_many: both sides several (a job has several tags). one_to_one: exactly one each way. Defaults to many_to_many, which is rarely what a business model means, say it."
                }
              },
              "additionalProperties": false
            },
            "minItems": 1,
            "description": "Typed columns of the board"
          },
          "description": {
            "type": "string",
            "description": "One line on what a row is"
          }
        },
        "additionalProperties": false
      },
      "minItems": 1,
      "description": "The boards (tables) of the backend, in any order"
    },
    "project": {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Project name, e.g. \"Bike Repair Shop\""
        },
        "description": {
          "type": "string",
          "description": "One line on what the system is for"
        }
      },
      "description": "The project that holds the boards",
      "additionalProperties": false
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; needed only when the account belongs to several (the error then lists them)"
    }
  },
  "additionalProperties": false
}
    arguments 162 lines
  • create_automation unknown never probed

    Create an automation on a board: when something happens, do something. The most useful action here is http_request, which calls an external API and writes the answer back into columns, pair it with the "scheduled" trigger and the board keeps itself up to date (prices, exchange rates, shipment status, weather). Triggers: item_created, status_changed, column_value_changed, date_approaching, scheduled. Actions: http_request, send_notification, send_email, change_status, set_column_value, create_cross_board_item, send_webhook. Two more things every action list can use: a { type: "delay", config: { minutes | hours | days } } action pauses the run and resumes the actions after it later (reminders, follow-ups); and any network action (http_request, send_webhook, send_email, send_whatsapp) may carry config.retry: { attempts (1-5), delaySeconds (1-60) }. send_webhook accepts config.secret for an HMAC signature. create_cross_board_item copies a new row to another board: config { targetBoardId, title?: "{{item.title}}", columnValues: { "<column id on the TARGET board>": "{{<column NAME on this board>}}" } }; there is no mapping field, and a column left out is not copied. To act only on some rows pass conditions, e.g. [{ field: "<column id on this board>", operator: "equals", value: "New seller" }]. Change an automation later with update_automation; call list_automations first so you do not add a second one that does the same thing.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "name",
    "trigger",
    "actions"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "actions": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "type",
          "config"
        ],
        "properties": {
          "type": {
            "type": "string",
            "description": "Column type: text, rich_text, number, status, date, datetime, duration, people, checkbox, dropdown, label, priority, link, email, phone, relation, lookup, rollup, rating, currency, file"
          },
          "config": {
            "type": "object",
            "description": "Action-specific config, e.g. { url, method, headers, responseMapping } for http_request",
            "additionalProperties": {}
          }
        },
        "additionalProperties": false
      },
      "description": "e.g. [{ type: \"http_request\", config: { url: \"https://api.frankfurter.app/latest?from=USD&to=ILS\", method: \"GET\", responseMapping: [{ path: \"rates.ILS\", columnId: \"<column id from get_board_schema>\" }] } }]"
    },
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "trigger": {
      "enum": [
        "item_created",
        "status_changed",
        "column_value_changed",
        "date_approaching",
        "scheduled"
      ],
      "type": "string",
      "description": "Event that starts the automation: item_created, status_changed, column_value_changed, date_approaching, or scheduled (cron)"
    },
    "isActive": {
      "type": "boolean",
      "description": "Whether it is active"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "conditions": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "field",
          "operator"
        ],
        "properties": {
          "field": {
            "type": "string",
            "description": "A column id on this board (from get_board_schema), or status, priority, title"
          },
          "value": {
            "description": "The value to compare with"
          },
          "operator": {
            "type": "string",
            "description": "equals, not_equals, contains, not_contains, is_empty, is_not_empty, greater_than, less_than"
          }
        },
        "additionalProperties": false
      },
      "description": "Run only for rows that match, e.g. [{ field: \"<column id>\", operator: \"equals\", value: \"New seller\" }]"
    },
    "triggerConfig": {
      "type": "object",
      "description": "e.g. { cron: \"0 8 * * *\" } for scheduled, { columnName } for column_value_changed",
      "additionalProperties": {}
    }
  },
  "additionalProperties": false
}
    arguments 94 lines
  • update_automation unknown never probed

    Change an existing automation: its actions, conditions, trigger config or name, or switch it off with isActive false. Fields left out stay as they are; actions and conditions, when given, replace the whole list. Use it to fix an automation instead of creating a second one next to it. Get the id from list_automations.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId",
    "automationId"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "New name"
    },
    "actions": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "type",
          "config"
        ],
        "properties": {
          "type": {
            "type": "string",
            "description": "Action type, as in create_automation"
          },
          "config": {
            "type": "object",
            "description": "Action-specific config",
            "additionalProperties": {}
          }
        },
        "additionalProperties": false
      },
      "description": "The full new list of actions (replaces the old one)"
    },
    "boardId": {
      "type": "string",
      "description": "Board id the automation belongs to"
    },
    "isActive": {
      "type": "boolean",
      "description": "false switches it off, true on"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "conditions": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "field",
          "operator"
        ],
        "properties": {
          "field": {
            "type": "string",
            "description": "A column id on this board (from get_board_schema), or status, priority, title"
          },
          "value": {
            "description": "The value to compare with"
          },
          "operator": {
            "type": "string",
            "description": "equals, not_equals, contains, not_contains, is_empty, is_not_empty, greater_than, less_than"
          }
        },
        "additionalProperties": false
      },
      "description": "Run only for rows that match, e.g. [{ field: \"<column id>\", operator: \"equals\", value: \"New seller\" }]"
    },
    "automationId": {
      "type": "string",
      "description": "Automation id (from list_automations)"
    },
    "triggerConfig": {
      "type": "object",
      "description": "New trigger config",
      "additionalProperties": {}
    }
  },
  "additionalProperties": false
}
    arguments 85 lines
  • list_automations unknown never probed

    List the automations on a board, so you can see what already runs before adding another.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "projectId",
    "boardId"
  ],
  "properties": {
    "boardId": {
      "type": "string",
      "description": "Board id (from list_boards / create_board)"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • search unknown never probed

    Full-text search across the projects, boards and items of the organization. Returns { results: [{ id, title, url }] }, the shape ChatGPT connectors and deep research expect; pass a result id to fetch for the full record. When you already know the board, query_items is cheaper and complete.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "description": "Max results, default 20",
      "exclusiveMinimum": 0
    },
    "query": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Search text"
    },
    "projectId": {
      "type": "string",
      "description": "Limit the search to one project"
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • fetch unknown never probed

    One project, board or item in full, by the id search returned (project:<id>, board:<projectId>:<boardId>, item:<projectId>:<boardId>:<itemId>) or by an app URL path. Returns { id, title, text, url, metadata }, the ChatGPT fetch contract; text is the record as JSON.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "An id from search, or an app URL path such as /projects/…/boards/…/items/…"
    },
    "organizationId": {
      "type": "string",
      "description": "Only needed for project ids when the credential has no default organization; otherwise resolved automatically"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • deploy_frontend unknown never probed

    Deploy a static frontend to TaskLite hosting and get a live URL https://{slug}.tasklite.dev (HTTPS, auto-published on first deploy, versions kept for rollback_deployment). Hand over the frontend in ONE of three ways: `files`, the files inline (path + content), the way to go from ChatGPT or any hosted client: write index.html and its assets, then deploy in the same turn; `zipUrl`, a public https URL of a zip (a Lovable/Bolt export, a GitHub release asset); `dir`, a build output folder on this machine (only when the MCP runs locally next to the files); `fromAppId`, a version already hosted in the same organization, copied on the server (start a new app from an existing site, or bring an old version back as a new one; get_deployment_files reads a version first). A real build that already exists on the person's machine fits none of these from a hosted server: tell them to drop the zip on the app's Versions screen (the adminUrl of the app, then Versions), which deploys the same way and keeps the same version history. In the frontend, call the app API via relative /api/{endpoint}, the hosting proxy injects the app identity, so no key ships to the browser.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "dir": {
      "type": "string",
      "description": "Local path to the BUILD OUTPUT directory (the one containing index.html), not the project root. Only where the MCP runs on the same machine as the files"
    },
    "appId": {
      "type": "string",
      "description": "App UUID or slug (app-xxxxxx), see list_apps"
    },
    "files": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path",
          "content"
        ],
        "properties": {
          "path": {
            "type": "string",
            "description": "Path inside the site, e.g. \"index.html\", \"app.js\", \"css/style.css\""
          },
          "content": {
            "type": "string",
            "description": "File content. Text as-is; binary as base64 with encoding \"base64\""
          },
          "encoding": {
            "enum": [
              "utf8",
              "base64"
            ],
            "type": "string",
            "description": "Default utf8"
          }
        },
        "additionalProperties": false
      },
      "maxItems": 500,
      "description": "The site files inline. Must include index.html. Up to 500 files / 8MB decoded, right for a frontend written in the conversation"
    },
    "zipUrl": {
      "type": "string",
      "format": "uri",
      "description": "Public https URL of a zip of the BUILD OUTPUT (index.html at the root, or inside a single top-level folder). Up to 50MB"
    },
    "fromAppId": {
      "type": "string",
      "description": "Deploy a version that is already hosted, copied on the server: another app in the same organization (start a new app from it), or this same app (bring an old version back as a new one). Nothing passes through the conversation, so any size works"
    },
    "fromVersion": {
      "type": "integer",
      "description": "With fromAppId: which version to copy (from list_deployments). Default: the live one",
      "exclusiveMinimum": 0
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 67 lines
  • list_deployments unknown never probed

    List the hosted-frontend deployments of an app, versions, which one is live, and the public URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • publish_app unknown never probed

    Publish an app, required before its API endpoints accept external calls.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • list_organizations unknown never probed

    List the organizations the authenticated user belongs to. Use the returned id as organizationId in other tools.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • create_app unknown never probed

    Create an app, a named API surface over the boards of a project, for an external frontend. Then add endpoints and an API key.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name",
    "projectId"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name"
    },
    "projectId": {
      "type": "string",
      "description": "Project id (from list_projects / create_project)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • get_frontend_prompt unknown never probed

    Get a ready-made prompt describing the app backend, for pasting into a frontend generator (v0/bolt/lovable/cursor). appId accepts the app UUID or its slug (app-xxxxxx), use list_apps to find it.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "tool"
  ],
  "properties": {
    "tool": {
      "enum": [
        "v0",
        "bolt",
        "lovable",
        "cursor",
        "claude-code"
      ],
      "type": "string",
      "description": "Target tool the prompt is written for"
    },
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • rollback_deployment unknown never probed

    Point the live URL back at a previous deployment version (see list_deployments for available versions).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "version"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "version": {
      "type": "integer",
      "description": "Deployment version number (from list_deployments)",
      "exclusiveMinimum": 0
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • get_deployment_files unknown never probed

    Read back what a hosted frontend version is made of: every file with its size and its URL on that version, and the full text of the text files (HTML, CSS, JS, JSON, SVG...). This is how a new conversation continues a site an earlier one built: "take my Krispool site and keep going" starts here, not from scratch. For a site written by hand the files ARE the source. For a bundled build (Vite, React) the JS is minified output: fine to inspect, not something to edit, so ask for the project's source instead. Images and other binaries come back as URLs only. Text is capped at 512KB per file and 4MB per call; narrow with `paths` for a big site. To start another app from this version, or bring an old version back as a new one, use deploy_frontend with fromAppId.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App id or slug (from list_apps / create_app)"
    },
    "paths": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Only these files, as listed by a previous call, e.g. [\"index.html\", \"css/site.css\"]"
    },
    "version": {
      "type": "integer",
      "description": "Version to read (from list_deployments). Default: the live version",
      "exclusiveMinimum": 0
    },
    "includeContent": {
      "type": "boolean",
      "description": "false lists the files without their text, a cheap first look at a large site. Default true"
    },
    "organizationId": {
      "type": "string",
      "description": "Organization id; defaults to the credential organization when omitted"
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6f84e86c916a4953/badge.svg)](https://brick.blue/agent/6f84e86c916a4953)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.