Do I need a different account per client?

No. One TaskLite account, connected from as many clients as you like. Each connection can be revoked separately.

Why does Cursor show fewer tools than Claude Code?

Some clients cap the number of tools they load per server. Both transports expose all 31; check the client's MCP settings for a tool limit.

Can two people share one key?

They can, but every action is then attributed to the key's owner in the audit log. Give each person their own key or their own OAuth connection.

Using the TaskLite connector from Cursor, Codex and Claude Desktop

Claude Desktop and claude.ai

Settings, Connectors, find TaskLite in the directory (or "Add custom connector" with the URL https://mcp.tasklite.net/mcp).
Connect, sign in to TaskLite (or sign up on the spot), approve.
In a chat, open the + menu, Connectors, and make sure TaskLite is toggled on for that conversation.

If the tools do not show up on claude.ai web

Toggle the connector on inside the chat through the + menu, or use Claude Desktop, where a Settings-added connector is available immediately. This is a client-side behaviour of the web app; the server-side handshake completes either way.

Claude Code

Hosted, with OAuth in the browser on first use:

claude mcp add --transport http tasklite https://mcp.tasklite.net/mcp

Or with a personal API key (TaskLite app, Settings, Integrations, API keys), which is what CI and scripts use:

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

Or the local package over stdio:

npm install -g @tasklite/mcp
claude mcp add tasklite -- tasklite-mcp

Verify with /mcp: tasklite should list 31 tools.

Cursor

Cursor reads MCP servers from .cursor/mcp.json in the project or ~/.cursor/mcp.json globally. Streamable HTTP with a key:

{
  "mcpServers": {
    "tasklite": {
      "url": "https://mcp.tasklite.net/mcp",
      "headers": { "Authorization": "Bearer tl_your_key" }
    }
  }
}

Or stdio through the package:

{
  "mcpServers": {
    "tasklite": {
      "command": "tasklite-mcp",
      "env": { "TASKLITE_API_KEY": "tl_your_key" }
    }
  }
}

Restart Cursor; the tools appear under MCP in the agent panel.

OpenAI Codex

Codex CLI takes MCP servers in ~/.codex/config.toml:

[mcp_servers.tasklite]
command = "tasklite-mcp"
env = { TASKLITE_API_KEY = "tl_your_key" }

Streamable HTTP is supported in recent Codex versions with a url key and http_headers; if your version rejects it, the stdio form above always works.

Any other MCP client

Anything that runs a stdio server can run tasklite-mcp with TASKLITE_API_KEY in the environment. Anything that supports Streamable HTTP can use the hosted URL with a bearer header. The server also publishes /.well-known/oauth-protected-resource, so clients that implement OAuth discovery can connect with no key at all.

Keys versus OAuth

	OAuth (hosted)	API key
Best for	Personal use in Claude apps	Editors, CI, scripts, shared machines
Scope	You, short-lived tokens, revocable in TaskLite	You (personal key) or an app (app key), revocable in TaskLite
Setup	Browser sign-in once	Paste once
Risk	Lowest	Treat like a password; never commit it

The TaskLite connector in Cursor, Codex, Claude Desktop and Claude Code