Taskive

ai.taskivePublished by taskive.aiOfficial publisherv1.0.0Updated Oct 24, 2026

AI-native project management + agent memory: tasks, sprints, risk, burnout, knowledge search.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Taskive is a remote MCP server for AI-native project management and agent memory, covering tasks, sprints, risk, burnout and knowledge search.

What you can do
Manage tasks and sprints in an AI-native project management workspace, as described in the registry entry. Assess project risk and team burnout signals. Search project knowledge and use it as agent memory. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Consider it when an assistant should work inside a project management workspace, tracking tasks and sprints, flagging risk or burnout, and recalling project knowledge across sessions.
Requirements
A remote streamable HTTP endpoint at mcp.taskive.ai. OAuth authentication is required, so a Taskive account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your Taskive workspace, which likely includes project, task and team data. Expect the assistant to read and possibly change tasks, sprints and knowledge entries; confirm before letting it write. Project and team data is sent to a third-party service.

Installation

In SourceWeft

  1. Open Taskive 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/ai.taskive%2Fmcp/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": {
    "taskive": {
      "type": "http",
      "url": "https://mcp.taskive.ai/mcp"
    }
  }
}

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.0LatestSep 16, 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.