ChatGPT and Claude Desktop can connect to Taskavel through OAuth. This is the preferred setup when the client provides a browser connector flow because you approve access directly in Taskavel instead of handling a long-lived token yourself.
Use this endpoint in either client:
https://taskavel.com/mcp/taskavel
The resulting connection uses your Taskavel identity. It does not grant the client broader access than you already have: project membership and role checks continue to control what the client can read or change.
ChatGPT
In ChatGPT, open Settings → Apps → Advanced, choose Create app, and enter the Taskavel MCP URL. Start the connection and follow the Taskavel OAuth approval page. Sign in to the intended Taskavel account before approving; this is especially important if the browser has more than one account session.
When ChatGPT returns to the conversation, begin with a read request. “List my Taskavel projects” is a useful first check because it confirms the connected account and exposes only information you can already access. If the result is incomplete, do not solve it by creating another app or sharing a PAT. Check the selected Taskavel account and its project memberships first.
Claude Desktop
In Claude Desktop, open Settings → Connectors → Add custom connector, enter the Taskavel MCP URL, and finish the OAuth approval in the browser. Return to Claude Desktop after the approval completes. The client UI can change independently, so use its current equivalent if a menu label differs.
Verify the connector with a request that does not mutate data, such as “Show my Taskavel tasks due this week.” After that succeeds, use detailed prompts for any write request: identify the project, the task, and the intended change. For example, “In Website, move task #42 to Review” is easier to verify than “Clean up my board.”
Manage a connected client
Taskavel shows OAuth-connected agents separately from personal access tokens under Account Settings → AI Integration (MCP). Disconnecting an OAuth client revokes that client’s connection. It does not invalidate any PAT you may have created for a CLI client, so review those separately if a device is lost or access should end.
Avoid creating duplicate connections simply to fix a stale result. First inspect the connected account, relevant project membership, and any role restriction. If you do need to reconnect, disconnect the old OAuth client, then run the connector flow again. Troubleshooting covers common connection and tool-access failures.