Tack

io.github.ThefirstmannnnPublished by GitHub account Thefirstmannnnv0.1.0Updated Oct 24, 2026

Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Tack is a task management MCP server that gives an assistant scoped OAuth access to issues, projects, and docs.

What you can do
Tack is described as task management for people and AI agents. It exposes issues, projects, and docs to an assistant through scoped OAuth access, so the assistant can work with those task-tracking objects. The registry description does not list individual tools or detail which operations are supported.
When to use it
Consider it when you want an assistant to read or work with issues, projects, and docs held in Tack alongside your own task tracking. It is less useful if you do not already use Tack or need capabilities beyond issues, projects, and docs.
Requirements
It runs as a remote streamable HTTP endpoint at the provider's domain, so no local runtime or package is needed. The description mentions scoped OAuth access, so an OAuth authorization for the relevant scopes is likely required. The manifest declares no authentication method, environment variables, or headers.
Before you install
The description refers to scoped OAuth access to issues, projects, and docs, so review which scopes are granted and whether the assistant can change or delete that data. The manifest declares no authentication details, so confirm the actual authorization flow before connecting. The homepage is a placeholder domain, which makes the real endpoint worth verifying.

Installation

In SourceWeft

  1. Open Tack in the dashboard and add it to a workspace.
  2. 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/io.github.Thefirstmannnn%2Ftack/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": {
    "tack": {
      "type": "http",
      "url": "https://your_domain/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 17, 2026

Score

35% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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