@tasklite/mcp

@tasklite/mcp

Documentation: https://tasklite.net/docs

TaskLite MCP server — build a full backend (projects, boards, typed columns, data, REST endpoints with API keys) from Claude Code, and hand your client a ready-made admin.

Setup

Install the package (and Claude Code if you don't have it), then add the server by its binary — this avoids a known Windows issue where claude mcp add mis-parses npx -y.

npm install -g @anthropic-ai/claude-code @tasklite/mcp
claude mcp add tasklite -- tasklite-mcp

Add -s user to claude mcp add to make it available in every project (claude mcp add -s user tasklite -- tasklite-mcp); the default scope is the current project only.

Then just tell Claude what you want to build — the sign_up tool creates your account, organization, and connection from the conversation (a strong random password is generated locally and never shown; use "forgot password" with your email for web access).

Already have an account? Create a key at TaskLite → Integrations → "Connect Claude Code" and use:

claude mcp add tasklite -e TASKLITE_API_KEY=tl_xxx -- tasklite-mcp

Hosted (no install)

Point any MCP client at the hosted server — nothing to install locally:

claude mcp add --transport http tasklite https://mcp.tasklite.net/mcp \
  --header "Authorization: Bearer tl_xxx"

The hosted server is stateless: every request carries its own credential, so one endpoint serves every account safely.

Simplest of all — the connector. In Claude (claude.ai or the desktop app), Settings → Connectors → add TaskLite, or add it by address using the URL above. You sign in once over OAuth; there is no key to create or store. Note that the tools appear in a new chat, not in the conversation you were already in.

Optional env: TASKLITE_API_URL (default https://api.tasklite.net), TASKLITE_APP_URL (default https://app.tasklite.net).

Typical flow (what Claude Code does)

• create_project → create_board → create_column × N — the schema.
• create_item / query_items — seed and inspect data.
• create_app → create_app_endpoint (with exposedColumns + RLS) → create_app_api_key — the REST surface for your frontend.
• get_app_spec / get_frontend_prompt — generate the frontend against it.
• Every tool returns an adminUrl — the ready-made admin for the end client.

Security model

• The tl_ key is exchanged for a short-lived JWT (POST /public/v1/auth/session); all calls run with the key owner's own permissions, never super-admin.
• App API keys belong in server-side env vars (Next.js API routes) — never in browser code.

Development

npm install
npm run build
TASKLITE_API_KEY=tl_xxx TASKLITE_API_URL=http://localhost:3333 node dist/index.js