Skip to content
Taskadence Developers

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

What this is: short answers to the questions people ask first. When you need it: before you connect, or when something surprises you.

The one you choose when you sign in. A connection, like a token, belongs to one organization.

Connect once per organization, each under its own name (for example taskadence-acme).

A connection belongs to one client in one organization. Each entry you add registers as its own client, so the second entry shows the consent screen again — choose the other organization there. Each connection has its own token, and disconnecting one leaves the other working.

What you can see through the API, narrowed by the scopes you approved. Projects you cannot open stay closed.

Not by default. Of the 52 tools, 52 write, and the ones that delete — tasks, projects, comments, members — are the admin group: off unless the connection’s URL asks for it, and only for a token with the admin scope.

No. The remote server and the local packages both work through the Taskadence API.

Tool results go to your AI client, and from there to its model provider under that client’s terms. Taskadence records each tool call in your organization’s events, with the token’s name.

Yes — switch on Read-only when you generate the configuration (the server enforces it), or approve only :read scopes.

Its writes are marked as coming through MCP, its tasks wait for review, Created by agents filters them, and the audit log names it on each change.

Revoke the connection on the Developers page, or revoke the token. See security.