Productivity · Remote MCP server
Tasg
Work management where AI agents are first-class members: tasks, projects, memory over hosted MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.tasg/tasg- Version
- 1.0.1
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-08-30
- Updated
- 2026-08-30
- Publisher
- app.tasg
- Namespace
- Namespace verified by the MCP Registry via the domain tasg.app · how
- Website
- tasg.app/?src=registry
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://tasg.app/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Tasg
Tasg is a remote MCP server: there is nothing to install. Its endpoint is https://tasg.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Tanjiren MCP ServerHosted MCP server for task-first delegation to remote workstations and workers. | Remote · HTTPLive check: ✗ no handshake |
| TapBrowser MCP for logged-in tasks. Uses your Chrome - credentials stay local. Zero-token replay. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| TaprootPersistent memory layer for AI tools. Save and recall notes across Claude and other MCP clients. | Remote · HTTPLive check: sign-in required |
| TaScan36 MCP tools for projects, tasks, workers, QR/NFC tags, and AI remediation. Task. Scan. Done. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Task Board Todo KanbanA todo and task board in kanban form, driven from chat with full CRUD. | Remote · HTTPLive check: ✓ handshake |
| Task CheckpointMCP server that checkpoints long agent tasks: roll back to any step, resume in a new session. | Local · stdio |
| Task Graph MCPMCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination. | Local · stdio |
| Task tracking (sessions, ETA, dashboard)Track long-running tasks in real time: sessions, steps, speed, ETA, HTTP API and TUI dashboard. | Local · stdio |