Use the Taskavel MCP server when an AI client needs authenticated access to your Taskavel work. Before connecting, decide whether the client can complete OAuth in a browser or whether it needs a personal access token. The answer determines how the client proves its identity to Taskavel.
The public Taskavel endpoint is:
https://taskavel.com/mcp/taskavel
If you use a self-hosted Taskavel instance, copy the URL displayed in Account Settings → AI Integration (MCP) instead. Do not replace the production URL with an example hostname from a configuration snippet.
Use OAuth for connector clients
OAuth is the right choice for a client that offers an interactive “add connector” or “add app” flow. It redirects you to Taskavel, where you sign in if necessary and approve the connection. The client then operates as your Taskavel user and remains subject to your normal project memberships and role restrictions.
ChatGPT and Claude Desktop have documented connector paths in the next guides. Add only the Taskavel endpoint above, then complete the approval in Taskavel. Do not create or paste a personal token for a client that can use the OAuth flow.
After authorizing, open the client and ask a harmless question such as “List my Taskavel projects.” A successful response confirms both the MCP connection and the effective account. If no expected projects appear, verify the Taskavel account and project membership before reconnecting.
Use a PAT for CLI clients
Claude Code, Codex, and similar command-line configurations normally use a personal access token. In Taskavel, open Account Settings → AI Integration (MCP) and create a token with a specific name, for example the client and machine that will use it. Copy the value when it is shown and place it only in a local secret store or environment variable.
Configure the client with the endpoint and an Authorization: Bearer header. Never commit a token in a repository, include it in a screenshot, or paste it into a shared configuration file. A named token per client or machine makes a later revocation precise.
Verify the setup before using write tools
First ask the client to discover data: list projects, list your tasks, or inspect a single known task. Confirm that the response matches the logged-in Taskavel account. Next, try a low-risk request such as retrieving a board snapshot. Only then ask the client to create, move, or update work.
Connection errors are usually endpoint or authentication errors; missing data is usually an account, membership, or role issue. See troubleshooting for the ordered checks, and read security and revocation before distributing a PAT.