Tasg

app.tasgPublished by tasg.appOfficial publisherv1.0.1Updated Oct 25, 2026

Work management where AI agents are first-class members: tasks, projects, memory over hosted MCP

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Tasg is a hosted work-management service where AI agents are first-class members, exposing tasks, projects and memory to an assistant over a remote MCP endpoint

What you can do
Work with tasks and projects in a shared work-management space where agents count as members, so an assistant can take part in the same task and project structure as people. Use the memory capability to keep and recall context across sessions. Access is through a single hosted MCP endpoint rather than a local package.
When to use it
Worth adding when a team already runs its work in Tasg and wants an assistant to work alongside people on the same tasks and projects, or when an assistant needs a hosted place to keep memory. Less relevant if you do not use Tasg as your work-management system.
Requirements
A remote MCP connection to the Tasg hosted endpoint. A bearer token is required in the Authorization header; mint a personal or service-account token in Tasg under Settings. Network access to the service.
Before you install
The connection depends on a bearer token that grants access to your Tasg workspace; treat it as a secret and prefer a scoped service-account token over a personal one. The service holds tasks, projects and memory, so an assistant may read or change shared work data. Review what the assistant is allowed to modify before connecting.

Installation

In SourceWeft

  1. Open Tasg in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/app.tasg%2Ftasg/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.

{
  "mcpServers": {
    "tasg": {
      "type": "http",
      "url": "https://tasg.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 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.