MCP

Connect Cursor to Taskavel

Create a personal access token, add the Taskavel MCP server to Cursor, and manage tasks, comments and timers from your editor.

Cursor connects to remote MCP servers through an mcp.json file. Connect it to Taskavel with a personal access token (PAT), sent as an Authorization: Bearer header. Treat the token 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 cursor-work-laptop. Copy the value when it is shown and store it in an environment variable, for example TASKAVEL_MCP_TOKEN, set in your shell profile or system environment. Do not paste the token into a file that is committed to a repository.

Add Taskavel to mcp.json

Use ~/.cursor/mcp.json to make Taskavel available in every project, or .cursor/mcp.json in one project. Add this entry:

{
    "mcpServers": {
        "taskavel": {
            "url": "https://taskavel.com/mcp/taskavel",
            "headers": {
                "Authorization": "Bearer ${env:TASKAVEL_MCP_TOKEN}"
            }
        }
    }
}

Cursor replaces ${env:TASKAVEL_MCP_TOKEN} with the value of the environment variable, so the file itself holds no secret. Remote servers do not support envFile, so the variable must be set in the environment Cursor starts from. Restart Cursor after you set it.

This syntax follows Cursor's MCP documentation (cursor.com/docs/context/mcp, checked October 2026). If Cursor changes its format, follow its current documentation and keep the same URL and header.

Check the connection

Open Customize in the Cursor sidebar and confirm that taskavel is enabled and lists its tools. Then ask: “List my Taskavel projects.” Start with a request that only reads before you let Cursor change anything. If the server fails, open the Output panel, choose MCP Logs, and look for authentication errors.

Work within an explicit scope

Name the project and task in your request, for example: “In Website, add a comment to task #42 saying the API review is complete.” Taskavel enforces your project role through MCP. A token cannot make a guest into a member or an admin. Cursor asks for approval before each tool call by default.

If you retire the installation or think the token was exposed, revoke it in AI Integration (MCP). See CLI access tokens for the token lifecycle.

Frequently asked questions

Where do I create a token?

In Taskavel, open Account Settings → AI Integration (MCP) and create a personal access token. Name it after the installation, for example cursor-work-laptop, and copy the value when it is shown. It is shown only once.

Does Cursor support OAuth with Taskavel?

A personal access token sent as a Bearer header is the tested way to connect Cursor to Taskavel. OAuth is the tested path for ChatGPT and Claude Desktop.

What should I try first?

Start with a request that only reads, such as “List my Taskavel projects.” When that works, ask for a small change in a named project, for example a comment on one task.

How do I revoke the token?

Open Account Settings → AI Integration (MCP) and revoke the token for this installation. A revoked token cannot be restored, so create a new one if you still need access.

Last reviewed Oct 31, 2026