Retasc

com.retascPublished by retasc.comOfficial publisherv1.0.2Updated Oct 24, 2026

Retasc is a work queue for AI coding agents. The next agent picks up where the last one stopped.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Retasc is a hosted work queue for AI coding agents, letting an assistant hand off tasks so the next agent continues where the last one stopped.

What you can do
  • Retasc is described as a work queue for AI coding agents.
  • It lets agents pick up queued work items and continue from where a previous agent stopped.
  • No tool list is published, so the exact operations an assistant can call are not documented here.
  • It is reached as a remote endpoint rather than a local package.
When to use it
Consider it when several AI coding agents work on the same codebase or task list and you want work handed off between them instead of restarting context each time.
Requirements
A remote MCP endpoint at mcp.retasc.com over streamable HTTP. Authentication is OAuth and required; no environment variables or headers are declared. A Retasc account is presumably needed to authorize, though the input does not state this.
Before you install
OAuth access is required, so the assistant acts under your Retasc identity. The input does not describe which tools exist, whether they write, modify or delete queue items, or what task data is stored on Retasc's servers; review the provider's terms and permissions before connecting.

Installation

In SourceWeft

  1. Open Retasc 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.retasc%2Fretasc/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": {
    "retasc": {
      "type": "http",
      "url": "https://mcp.retasc.com/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

3
  1. v1.0.2LatestOct 20, 2026
  2. v1.0.1Oct 13, 2026
  3. v1.0.0Sep 16, 2026

Score

67% 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
  • 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.