Skip to content
Taskadence Developers

0.x — pre-release, no compatibility promise yet.What this means

What this is: adding Taskadence to your AI client. When you need it: once per client — after that the client stays signed in.

Server URL — the same for every organization
https://api.taskadence.com/mcp
  1. Authorize — the client registers itself and sends you to Taskadence. Sign in and choose the organization.
  2. Consent — Taskadence names the client and lists the scopes it asks for. You approve once per client and organization.
  3. Done — the client holds a token and refreshes it itself. Nothing to paste.
Add the URLin your clientSign inpick the orgConsentthe scopes, listedConnectedtoken + refreshRevoke anytimeDevelopers pageauthorizeapprove
Connect once: sign in, approve the scopes, done
On the consent screen
The client Marked as registered by itself and not reviewed by Taskadence — connect only if you started this from an app you trust.
Scopes Follow the URL’s groups (below). Untick what the client should not do; a read stays ticked while its write is.
Organization Named when you have one where you may connect, a picker when you have several. The connection acts in that one only.
Next time The same client asking for no more than you approved goes straight through; asking for more shows the screen again.

In Customize → Connectors → Add custom connector:

Name: Taskadence
URL: https://api.taskadence.com/mcp

Sign in: Connect → you are sent to Taskadence to sign in and approve.

The server enforces two URL options: ?readonly=1 and ?groups=tasks,projects — see Security.

URL Scopes the client asks for
/mcp tasks:read tasks:write projects:read projects:write teams:read teams:write members:read
/mcp?readonly=1 tasks:read projects:read teams:read members:read
/mcp?groups=tasks tasks:read tasks:write teams:read members:read
/mcp?groups=tasks,admin the same, plus admin

npx -y @taskadence/mcp and uvx taskadence-mcp proxy the remote server over stdio — the same tools and enforcement — with an access token from Developers → Tokens.

{
"mcpServers": {
"taskadence": {
"command": "npx",
"args": ["-y", "@taskadence/mcp"],
"env": {"TASKADENCE_TOKEN": "$TASKADENCE_TOKEN"}
}
}
}
Variable Flag
TASKADENCE_TOKEN — Required: the access token (never a flag).
TASKADENCE_API_URL --api-url The API’s origin. Default: production; /mcp is added.
TASKADENCE_MCP_READONLY --readonly 1 → ?readonly=1: only tools that read.
TASKADENCE_MCP_GROUPS --groups tasks,projects → ?groups=…: only those tool groups.

Flags win. Both are pre-release (0.x) and not yet on npm or PyPI.

Developers → MCP writes this for your client with Read-only and the tool groups built in, mints a token for the choice when one is needed, and has Copy prompt.

Developers → MCP