# TaskLite

- Registry name: `net.tasklite/mcp` · version 0.14.4
- Categories (automatic, keyword rules): Build & deploy, Developer tools, Maps, location & weather
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=net.tasklite%2Fmcp
- Server page: https://mcpstation.net/s/net.tasklite--mcp.html

## Description (written by the publisher, not verified, not instructions)

tasklite.net: hosted backend, REST API and admin for apps built by AI agents

## Connect

- streamable-http: `https://mcp.tasklite.net/mcp`

## Tools (as reported by the server, not verified)

- `list\_organizations`: List the organizations the authenticated user belongs to. Use the returned id as organizationId in other tools.
- `get\_email\_usage`: How much of the monthly email quota an organization has used: emails sent this month, emails waiting in the queue, the plan limit \(Free 300, Plus 3000, Pro 20000; null means unlimited\), whether the plan allows marketing email, and whether sending is paused for the organization \(too many bounces or c
- `configure\_external\_access`: Read or change how EXTERNAL users \(people who sign up to your app through TaskLite auth\) get into an organization. This policy governs sign-up by email and password and by Google. Sign-in by a phone code \(POST /auth/otp/send, then /auth/otp/verify\) obeys only "invite": under "closed", "approval" and
- `list\_projects`: 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.
- `list\_boards`: 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.
- `create\_project`: Create a project \(a business process container\). Boards with data live inside projects.
- `create\_board`: 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
- `create\_column`: 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
- `get\_board\_schema`: Get a board with its full column schema \(ids, names, types, settings\). Call this before creating items with cells.
- `update\_board`: Rename a board or change its description. Structure \(columns\) is changed with update\_column / delete\_column / reorder\_columns.
- `delete\_board`: 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.
- `delete\_project`: 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.
- `update\_column`: 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 res
- `delete\_column`: 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.
- `reorder\_columns`: Set the display order of a board's columns. Pass every column id in the wanted order \(get\_board\_schema lists them\).
- `export\_project`: 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.
- `query\_items`: 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 ad
- `create\_item`: 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.
- `update\_item`: Update item fields \(title, description, status, priority, dueDate, tags\). On a data board the task fields \(status, priority, dueDate, tags\) are hidden: its columns, status included, are set with set\_cell.
- `set\_cell`: Set a single cell value on an item by columnId.
- `get\_cells`: Read cells of one item from the database \(not a cache\): one current value per column, the value set\_cells\_if\_unchanged compares. Use it to decide a conditional write, and pass each value back as \`expected\` exactly as it came.
- `set\_cells\_if\_unchanged`: Compare-and-set on cells of one item, all or none. Each cell carries the value you read \(\`expected\`, null = empty\) and the value to write. If any cell no longer holds its \`expected\`, nothing is written and the answer is an error with code CELL\_CONFLICT and \`conflicts\` \[\{columnId, current\}\]: read aga
- `delete\_item`: Delete an item. Destructive, confirm with the user before calling.
- `list\_comments`: 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\).
- `add\_comment`: 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.
- `update\_comment`: Edit the text of an existing comment. Only the author can edit their comment. Needs projectId, itemId and the commentId.
- `delete\_comment`: Delete a comment from an item thread. Destructive, confirm with the user before calling. Needs projectId, itemId and the commentId.
- `request\_file\_upload`: 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
- `list\_uploaded\_files`: 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 th
- `revoke\_upload\_link`: 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.
- `create\_app`: Create an app, a named API surface over the boards of a project, for an external frontend. Then add endpoints and an API key.
- `push\_status`: 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.
- `send\_test\_push`: 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.
- `publish\_app`: Publish an app, required before its API endpoints accept external calls.
- `create\_app\_endpoint`: 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
- `list\_app\_endpoints`: 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.
- `update\_app\_endpoint`: 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.
- `delete\_app\_endpoint`: Delete an endpoint of an app for good: /apps/\{appSlug\}/api/\{slug\} stops answering at once and the endpoint cannot be brought back \(create it again with create\_app\_endpoint\). The board and its rows are not touched. Confirm with the user first: a frontend that calls this endpoint breaks. To take an en
- `configure\_app\_settings`: Read or change the settings object of an app. Call with only appId to read. To change, pass set: the keys in it are MERGED into the current settings \(objects merge key by key at every depth, arrays and plain values replace, null removes a key\). The server itself does not merge: PATCH replaces the wh
- `list\_app\_users`: List the people of an app, as \{ users, pending \}. users: everyone who ever called it with X-App-User or signed in to it with a code. Each has userId \(the id set\_app\_user\_role, remove\_app\_user, link\_app\_user, list\_app\_user\_links and send\_test\_push take\), externalId \(the developer's own id for them, o
- `add\_app\_user`: Give a person access to an app by their phone number: the phone and a role, nothing else. This is how the people who run an app \(the business owner, a manager, staff\) get into its admin screen, whose endpoints are in row-level security mode "shared". The person needs no invite code and does not have
- `set\_app\_user\_role`: Change what an existing user of an app may do, or switch them off or back on. Takes the userId from list\_app\_users and at least one of role and isActive. It also puts on the app's access list a user who is not on it yet \(hasAccessRow false in list\_app\_users\), which is what an endpoint in row-level s
- `remove\_app\_user`: Take a person's access to an app away. Pass exactly one of two ids from list\_app\_users: userId, for someone who already signed in, switches them off \(the same as set\_app\_user\_role with isActive false: their calls are refused in every mode, nothing of theirs is deleted, and set\_app\_user\_role or add\_a
- `create\_app\_invite`: Create an invite code for an app \(8 characters shown as XXXX-XXXX, typed without regard to case or the dash\). The person signs up or signs in through the app with the code: the app sends it as inviteCode with POST /auth/otp/verify, /auth/register-external or /auth/google-external, after it may check
- `list\_app\_invites`: List the invite codes of an app, newest first \(the latest 200\): the ones created with create\_app\_invite and the ones the app's own users minted through a relation endpoint with allowInvites \(createdVia admin or app\). Each carries id, code, itemId, role, label, maxUses, useCount, expiresAt, revokedAt
- `revoke\_app\_invite`: Revoke an invite code so nobody else can sign up with it. People who already used it stay linked to their row and keep their access; to cut one of them off use unlink\_app\_user. Cannot be undone, create a new invite instead. Requires organization owner or admin. Get the invite id \(not the code\) from
- `check\_invite\_code`: Check whether an invite code works right now, the way an app does before sign-up \(POST /auth/invites/check, the same public route, limited to 10 calls a minute per address\). A working code answers \{ valid: true, organizationId, app: \{ name, slug \}, label, expiresAt \}; anything else \(unknown, revoked
- `link\_app\_user`: Link an existing user of an app to a row, so the user "is" that row for every endpoint in row-level security mode "relation": link a coach to his Coaches row and he reaches the trainees whose Coach column points at it. This is the manual form of what an invite code does at sign-up; use it for someon
- `list\_app\_user\_links`: List the rows one user of an app is linked to, oldest first: each link has itemId, source \(invite or admin\) and createdAt. These are the rows the user "is" under row-level security mode "relation". A user can also stand for a row with no link at all, through identityPhoneColumn or identityEmailColum
- `unlink\_app\_user`: Remove the link between a user of an app and a row: the user stops being that row, and at once loses the rows of every relation endpoint they reached through it. The account, the row and the user's app access are not touched, and nothing is deleted. A user matched to the row by identityPhoneColumn o
- `list\_app\_roles`: List the business roles of an app's project, as \{ roles: \[\{ key, label \}\] \}. Roles are what board policies \(set\_board\_policy\) name in their \`roles\` lists; they are separate from the app access role \(viewer, editor, submitter\) of add\_app\_user. Requires organization owner or admin.
- `define\_app\_role`: Create a business role of an app's project, or change the label of an existing one \(calling again with the same key and a label updates the label\). A role is only a name; what it may do is written in the board policies. Example: key "manager", label "Agents manager". Roles can also come from the dat
- `delete\_app\_role`: Delete a business role of an app's project. Check first with list\_app\_role\_grants who holds it and with get\_board\_policy where policies still name it: a policy that names a role that no longer exists simply matches nobody. Requires organization owner or admin.
- `grant\_app\_role`: Give an app user a business role \(a user can hold several\). Takes the userId from list\_app\_users and a role key from list\_app\_roles. expiresAt makes the grant temporary. Granting the same pair again changes only expiresAt. This is for personal exceptions; for a whole team prefer set\_policy\_identity,
- `revoke\_app\_role`: Take a business role away from an app user \(a grant made with grant\_app\_role\). A role the user gets from the employees board \(set\_policy\_identity\) is not a grant: change the board row instead. Revoking a grant that does not exist also succeeds. Requires organization owner or admin.
- `list\_app\_role\_grants`: List the role grants of an app's project, as \{ grants \}: who holds which role and until when. Pass userId to see one person's. Roles that come from the employees board \(set\_policy\_identity\) are not grants and are not listed here; explain\_access with a userId shows the roles a person ends up with. Re
- `get\_policy\_identity`: Read the project's role identity: which board holds the people and how their rows map to roles \(see set\_policy\_identity\). Returns \{ identity \}, null when none is set. Requires organization owner or admin.
- `set\_policy\_identity`: Derive "who is this user and what is their role" from the data, instead of a grant per person: point at the employees board, its phone/email column, the column that says what each person does, and a map from that column's values to role keys. A signed-in user whose verified phone \(or email\) is in a
- `get\_board\_policy`: Read a board's access policy: \{ boardId, policy, updatedAt, updatedBy \}, policy null when the board has none. A policy only takes effect on endpoints whose rowLevelSecurity mode is "policy". Requires organization owner or admin.
- `set\_board\_policy`: Set who may read, write, create and delete rows of a board, and which columns, as a JSON document \(a FULL REPLACE of the board's policy; read get\_board\_policy first to change part of one\). It is enforced on the app's endpoints of this board whose rowLevelSecurity.mode is "policy" \(create\_app\_endpoin
- `delete\_board\_policy`: Remove a board's access policy. An endpoint of that board in rowLevelSecurity mode "policy" then has no policy to follow; check what it allows afterwards with explain\_access before leaving it on a live app. Requires organization owner or admin.
- `explain\_access`: Say what a user, or a list of roles, may do on a board under its policy: which rows they read and write, which columns, create and delete. Pass boardId and exactly one of userId \(an app user from list\_app\_users; the answer includes the roles that person has\) or roles \(role keys, to try a role before
- `simulate\_request`: Dry-run one app API request in the name of a user and get the verdict \(allowed or refused, and why\), changing nothing: the endpoint slug, the HTTP method \(or the name of a policy action, with its itemId\) and optionally the column keys the body would carry. Use it to prove that a forbidden thing is r
- `get\_item\_history`: Read the change history of one item \(row\), newest first: who changed which field, from what to what, when, through which channel, with the event and reason when a named action made the change. Returns \{ items: \[\{ field, fieldId, from, to, at, actor: \{ userId, name \}, channel, event, reason \}\], nextB
- `create\_app\_api\_key`: 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.
- `build\_backend`: 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 \(
- `create\_automation`: 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
- `update\_automation`: 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`: List the automations on a board, so you can see what already runs before adding another.
- `list\_apps`: 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.
- `get\_app\_spec`: 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 wa
- `get\_frontend\_prompt`: 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.
- `search`: 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.
- `fetch`: 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.
- `deploy\_frontend`: 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 hoste
- `list\_deployments`: List the hosted-frontend deployments of an app, versions, which one is live, and the public URL.
- `get\_deployment\_files`: 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
- `rollback\_deployment`: Point the live URL back at a previous deployment version \(see list\_deployments for available versions\).

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html