Tasklix

dev.tasklixPublished by tasklix.devOfficial publisherv0.1.0Updated Oct 24, 2026

The shared task board your autonomous agent fleet can read and write.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Tasklix is a remote MCP server that gives an assistant read and write access to a shared task board used by a fleet of autonomous agents.

What you can do
  • Read and write tasks on a shared task board
  • Coordinate work between multiple autonomous agents through that board
  • (No tool list was supplied, so specific operations are not documented.)
When to use it
Consider it when several agents or assistants need a common place to track and hand off tasks, rather than each keeping its own state.
Requirements
Remote streamable HTTP endpoint at api.tasklix.dev; no local package or runtime. OAuth authentication is required. No environment variables or headers are declared.
Before you install
The server can write to a shared board, so an assistant may create or change tasks other agents rely on. Access is granted through OAuth, so review the scopes requested at sign-in. No tool list is published, so the exact write operations are not documented.

Installation

In SourceWeft

  1. Open Tasklix 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/dev.tasklix%2Ftasklix/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": {
    "tasklix": {
      "type": "http",
      "url": "https://api.tasklix.dev/mcp"
    }
  }
}

README

This repository has no README.

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. v0.1.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.