Troubleshooting

Message	Cause and fix
Send a Taskgert bot API token as "Authorization: Bearer tgt_live_…".	The client sends no token, or not as a bearer header. Fix the client's configuration (Connect).
The API token is not valid any more (revoked, expired, or its bot was deleted).	Create a new token on the bot's page and update the client.
This API token lacks the "tasks:write" scope … Ask the workspace owner for a token with that scope.	The token's scopes do not allow the action. Create a token with the scope named in the message.
… The bot's role in this project does not allow it; ask a project admin for a higher role.	The bot's role is too low for the action. Raise it in the project's Members page.
No task TGT-99 is visible to this bot. / No project with key "TGT" is visible to this bot.	It does not exist, or the bot is not a member of the project. Add the bot to the project.
The project has no column "Someday". Its columns are "To do", "Done".	Columns and labels are matched by name: use one of the names listed.
Someone changed it in the meantime. Read it again and retry with the current version.	The version passed was stale. Read the task again with get_task and retry.
Too many requests: …	Over the per-token rate limit. Wait and retry; spread bulk work out.
The request was not valid: …	An input is wrong; the lines after it name each field. A project's key cannot be changed at all (Concepts).
The client lists no tools	Check that the URL ends in /mcp and the transport is Streamable HTTP; then call whoami.

Still stuck? Call whoami: it shows the bot, its workspace and the token's scopes and expiry.

New tools do not show up

MCP clients load the tool list when they connect and keep it. After a new version of the server is deployed, a client that was already connected keeps the old list: the new tools are not there, and the agent may try to work around what it believes is missing.

• Check: call whoami. It says the server's version, how many tools it has (server.tools) and a short catalog fingerprint. If your client lists fewer taskgert tools, or the fingerprint changed since you last looked, its list is out of date.
• Fix: reconnect the MCP server. In Claude Code, run /mcp and reconnect taskgert; in other clients, restart the session or reload the server.

The server is stateless, so it cannot tell a connected client that its tools changed: the check has to come from the agent.