Claude Code is a command-line client, so connect it to Taskavel with a personal access token (PAT) rather than a browser OAuth connector. The token must be handled as a private credential for the Taskavel user who created it.
Create a dedicated token
In Taskavel, open Account Settings → AI Integration (MCP) and create a personal access token. Name it for this installation, for example claude-code-work-laptop. Copy the value at creation and put it into a local secret store or an environment variable that Claude Code can read. Do not put the token in a project repository or a checked-in configuration file.
Use the production endpoint:
https://taskavel.com/mcp/taskavel
For a self-hosted Taskavel instance, copy the endpoint from its AI Integration page instead. The token and endpoint belong together: a production token should not be placed in a configuration that points to another environment.
Add the remote MCP server
Add a remote server named taskavel through Claude Code’s current MCP configuration method. Set its URL to the Taskavel endpoint and provide the PAT as an Authorization: Bearer HTTP credential. Claude Code configuration formats can change, so use its current documentation for the exact command or file syntax. The important security property is that the token is referenced from private environment or secret storage, not embedded as plain text in a shared config.
Start a new Claude Code session after changing the configuration. Ask it to “List my Taskavel projects” before giving it a mutation. This confirms that the running process can read the token and that it is authenticated as the expected Taskavel user.
Work within an explicit scope
Ask Claude Code to inspect a task before editing it and name the project when a request might be ambiguous. A precise request such as “In Website, add a comment to task #42 saying the API review is complete” is easier to review than a broad request to update a backlog.
Taskavel enforces the connected user’s project role through MCP. A PAT supports the MCP connection but cannot elevate a guest to a member or an admin. Review the generated MCP tools reference before granting a workflow permission to write.
If you retire the installation or suspect the token was exposed, revoke the named token in AI Integration (MCP), then create a replacement only if needed. See CLI access tokens for the credential lifecycle.