When Taskavel MCP does not behave as expected, check the connection in order: endpoint, authentication method, connected account, project membership, role, and tool input. This order avoids replacing credentials or changing project data when the actual problem is a wrong URL or account session.
The client cannot connect or authenticate
For Taskavel’s public service, use exactly:
https://taskavel.com/mcp/taskavel
For a self-hosted installation, use the URL shown in Account Settings → AI Integration (MCP). Do not use a copied example host, a page URL, or an endpoint from a different environment.
ChatGPT and Claude Desktop should use their OAuth connector flow. Reopen the connector configuration, confirm the endpoint, and repeat Taskavel approval with the intended account. A CLI client needs a valid PAT supplied as an Authorization: Bearer credential. If the token has been revoked or was not retained at creation, create a new named token and update the client’s private secret setting; Taskavel does not reveal an existing token value later.
The server connects but expected work is absent
Ask the client to list accessible projects. If the project is not in that result, check the Taskavel account that approved OAuth or created the PAT. Then verify that account’s project membership. MCP does not bypass membership rules and cannot combine access from another account.
If the project is present but a name is ambiguous, ask the client to show the matching choices and use the returned project ID. Do the same with board columns, milestones, tags, and tasks before trying a write. A failed lookup is often an unclear identifier, not an authorization failure.
A write action is denied or does something unexpected
Check the connected user’s project role. Guests can read project content and watch tasks, but cannot modify tasks, comments, or attachments. Owner and admin actions such as member management require those roles. Do not retry under a colleague’s credential; change membership through the appropriate project owner if access is intended.
For unexpected input behavior, inspect the generated tool page. Tool schemas state the required fields, and descriptions clarify special cases. Task descriptions must be valid rich-text HTML rather than Markdown. A comment number shown as #123 identifies a comment, not a task. List existing milestones before creating one, and choose a real board column returned by the server.
A destructive operation is refused
Permanent deletion intentionally has two conditions: the task must already be archived and the call must include explicit confirmation. Inspect or archive the task first. If your goal is simply to remove it from active work, stop after archiving and review the result; deletion is not a general cleanup shortcut.
Still blocked
Collect the client name, the endpoint type (OAuth or PAT), the exact non-secret error, and whether a read-only request such as listing projects succeeds. Do not include a token in a report. This information distinguishes a connector problem from an account, role, or tool-input issue without exposing credentials.