TaskLite is an MCP server with 46 tools an agent can call, among them add_comment, build_backend, configure_external_access. It answers at https://mcp.tasklite.net/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
tasklite.net: hosted backend, REST API and admin for apps built by AI agents
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: projectId, itemId, content, mentionedUserIds, attachmentIds |
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 se Inputs: project, boards, api, organizationId |
configure_external_access | 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 organizatio Inputs: organizationId, registrationPolicy, appLoginUrl |
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. Inputs: name, projectId, organizationId |
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 Inputs: appId, name, scopes, organizationId |
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 Inputs: appId, boardId, slug, name, allowedMethods, exposedColumns |
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 keep Inputs: projectId, boardId, name, trigger, triggerConfig, actions |
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; "dat Inputs: projectId, name, description, kind |
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 mea Inputs: projectId, boardId, name, type, settings, isRequired |
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. Inputs: projectId, boardId, title, description, status, priority |
create_project | Create a project (a business process container). Boards with data live inside projects. Inputs: name, description, organizationId |
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. Inputs: projectId, boardId |
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. Inputs: projectId, boardId, columnId |
delete_comment | Delete a comment from an item thread. Destructive, confirm with the user before calling. Needs projectId, itemId and the commentId. Inputs: projectId, itemId, commentId |
delete_item | Delete an item. Destructive, confirm with the user before calling. Inputs: projectId, boardId, itemId |
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 Inputs: projectId, organizationId |
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 inli Inputs: appId, files, zipUrl, dir, organizationId |
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/{o Inputs: projectId, organizationId, maxItemsPerBoard |
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; te Inputs: id, organizationId |
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 Inputs: appId, format, organizationId |
get_board_schema | Get a board with its full column schema (ids, names, types, settings). Call this before creating items with cells. Inputs: projectId, boardId |
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. Inputs: appId, tool, organizationId |
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. Inputs: appId, organizationId |
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. Inputs: organizationId |
list_automations | List the automations on a board, so you can see what already runs before adding another. Inputs: projectId, boardId |
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. Inputs: projectId, page, limit |
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). Inputs: projectId, itemId, page, limit |
list_deployments | List the hosted-frontend deployments of an app, versions, which one is live, and the public URL. Inputs: appId, organizationId |
list_organizations | List the organizations the authenticated user belongs to. Use the returned id as organizationId in other tools. |
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. Inputs: organizationId, page, limit |
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 ho Inputs: itemId, organizationId |
publish_app | Publish an app, required before its API endpoints accept external calls. Inputs: appId, organizationId |
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 too Inputs: appId, organizationId |
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, prio Inputs: projectId, boardId, search, status, excludeStatus, priority |
reorder_columns | Set the display order of a board's columns. Pass every column id in the wanted order (get_board_schema lists them). Inputs: projectId, boardId, columnIds |
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 acco Inputs: itemId, clientName, clientEmail, clientPhone, message, maxFiles |
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. Inputs: tokenId, organizationId |
rollback_deployment | Point the live URL back at a previous deployment version (see list_deployments for available versions). Inputs: appId, version, organizationId |
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 kn Inputs: query, projectId, limit |
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. Inputs: appId, userIds, title, body, organizationId |
set_cell, update_app_endpoint, update_board, update_column, update_comment, update_item
Every block below points at https://mcp.tasklite.net/mcp. Pick your client and copy.
claude mcp add --transport http tasklite https://mcp.tasklite.net/mcp
{
"mcpServers": {
"tasklite": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.tasklite.net/mcp"]
}
}
}{
"mcpServers": {
"tasklite": {
"url": "https://mcp.tasklite.net/mcp"
}
}
}{
"servers": {
"tasklite": {
"type": "http",
"url": "https://mcp.tasklite.net/mcp"
}
}
}{
"context_servers": {
"tasklite": {
"url": "https://mcp.tasklite.net/mcp"
}
}
}{
"mcpServers": {
"tasklite": {
"serverUrl": "https://mcp.tasklite.net/mcp"
}
}
}{
"mcpServers": {
"tasklite": {
"url": "https://mcp.tasklite.net/mcp"
}
}
}name: TaskLite
version: 0.0.1
schema: v1
mcpServers:
- name: TaskLite
type: streamable-http
url: https://mcp.tasklite.net/mcp{
"mcpServers": {
"tasklite": {
"httpUrl": "https://mcp.tasklite.net/mcp"
}
}
}{
"mcpServers": {
"tasklite": {
"type": "http",
"url": "https://mcp.tasklite.net/mcp"
}
}
}{
"mcpServers": {
"tasklite": {
"url": "https://mcp.tasklite.net/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.tasklite.net%2Fmcp&type=streamable_http&id=tasklite&name=TaskLite
It answered our last check on 24 October 2026 in 149 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by tasklite.net and served from mcp.tasklite.net, the vendor's own domain: https://mcp.tasklite.net/mcp.
46, as returned by the server's own tools/list on 22 September 2026: add_comment, build_backend, configure_external_access, create_app, create_app_api_key, create_app_endpoint, create_automation, create_board, and 38 more.
It answered our last check on 24 October 2026 in 149 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.tasklite.net/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: net.tasklite. Endpoint host: mcp.tasklite.net. ARD identifier: urn:air:net.tasklite:mcp:mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.