mcpbeat Sign in

TaskFlow MCP Server

by denegra-taskflow Your server? Claim it
answering

TaskFlow is answering right now. Last checked 13 min ago.

Shared to-do memory for AI assistants: flows, tasks, inbox, meeting notes. Claim and hand off tasks.

Uptime history 17 hours of history
17 hours agonow
100.0%
Uptime 24h
62 of 62 checks
—
Tools
hidden behind auth
546 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check TaskFlow every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add taskflow --transport http https://taskflow.denegra.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://taskflow.denegra.ai/mcp
~/.codex/config.toml
[mcp_servers.taskflow]
url = "https://taskflow.denegra.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "taskflow": {
      "url": "https://taskflow.denegra.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "taskflow": {
      "type": "http",
      "url": "https://taskflow.denegra.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://taskflow.denegra.ai/mcp streamable-http sign-in 542 ms 13 min ago

Alternatives to TaskFlow

same job, measured the same way
Delimit
by delimit-ai

One workspace for every AI coding assistant. Shared tasks, memory, and governance.

local only
Fluent
by becomefluent

Your work meetings, notes, people, tasks and follow-ups from Fluent, in your AI assistant.

answering
Vibsync
by vibsync

One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.

answering
Evc Mesh MCP
by entire-vc

Tasks, comments, shared memory and handoffs for teams of people and AI agents, over MCP.

answering
Memdex
by choyugyeong

Shared memory for AI coding agents: summaries, symbol map, notes and agent-to-agent messages.

1 771 installs/wk local only
TestGraph
by bbcbasic

Shared semantic graph for AI reviews, classification and structured memory across AI assistants.

37 tools answering
Tincan
by gotincan

Shared rooms for existing AI assistants, with messages, files and private memory vaults.

62 tools answering
Reef
by reefwith

Shared, living memory for you and your people — coves your AI assistant can read and write.

answering

TaskFlow — questions

Answers built from our own checks of this server.

Why is there no tool list for TaskFlow?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is TaskFlow working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 62 of 62 checks got a reply (100.0%), average response time 546 ms. The bar chart above shows every period we have measured.
How do I connect TaskFlow?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to TaskFlow?
No API key is involved. TaskFlow answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is TaskFlow?
It answers our handshake in 546 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.