Taskavel

com.taskavelPublished by taskavel.comOfficial publisherv1.0.0Updated Nov 1, 2026

Headless task management for bots, apps and AI agents. Remote MCP server, OAuth or access token.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for headless task management, letting an assistant create and manage tasks for bots, apps and AI agents via OAuth.

What you can do
  • Manage tasks in a headless task system on behalf of bots, apps and AI agents.
  • Connect over a remote MCP endpoint with OAuth or an access token.
  • No tool list is published, so the exact task operations available are not documented here.
When to use it
Consider it when you want an assistant or agent to work with tasks in a hosted task management service rather than a local tool, and you are comfortable authorizing it through OAuth.
Requirements
A remote MCP endpoint at taskavel.com over streamable HTTP. OAuth authentication is required; an access token is also mentioned as an alternative. No environment variables or headers are declared.
Before you install
OAuth authorization grants the server access to your task data; review the scopes requested. The tool list is not published, so what the assistant can read or change is unclear before connecting. Task data is held by a third-party hosted service.

Installation

In SourceWeft

  1. Open Taskavel in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.taskavel%2Ftaskavel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "taskavel": {
      "type": "http",
      "url": "https://taskavel.com/mcp/taskavel"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.