Taskforce
Taskforce is a MCP server that connects AI coding agents to a shared task and planning workspace at Taskforce HQ.
About
Taskforce is a Model Context Protocol server backed by taskforcehq.ai that exposes a task and planning workspace tuned for people working alongside AI agents. Developers who juggle specs, todos, and agent sessions in separate places can register the remote MCP URL so their agent can read and update planning context in one system instead of re-pasting state into every prompt. The integration is HTTP-based remote MCP rather than a local skill file, which keeps setup lightweight if your editor already supports registry servers. It is an operational PM layer, not a code generator or deployment tool.
- Remote streamable-http MCP endpoint at mcp.taskforcehq.ai for agent clients
- Task and planning workspace built for human–AI collaboration on real work
- Published MCP registry schema with version 0.3.321 and GitHub source
- Branded remote server card suitable for Claude Code, Cursor, and other MCP hosts
- Focused on execution tracking, not generic chat memory
Taskforce by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http taskforce https://mcp.taskforcehq.ai/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
What it does
Connect your coding agent to a shared task and planning workspace so humans and AI stay aligned on what to build next.
Who is it for?
Best when you're running long agent sessions and want PM-style tasks and plans wired directly into Claude Code, Cursor, or Codex.
Skip if: Skip if you only need in-repo issues on GitHub with no external planning product or MCP setup.
What you get
After you add the remote MCP endpoint, your agent can work against a centralized task and planning workspace alongside you instead of guessing scope from scratch each session.
- Registered remote MCP connection to Taskforce planning APIs
- Agent-readable task and planning context in a shared workspace
- Ongoing sync between human priorities and agent execution
By the numbers
- MCP server version 0.3.321
- Single remote endpoint type: streamable-http
- Source repository: github.com/taskforcehq/taskforce
Recommended MCP Servers
0Latency MemoryPersistent memory layer for AI agents.
0nMCP — Universal AI API OrchestratorUniversal AI API Orchestrator — 1,554 tools, 96 services.
0xHumans Protocol MCPMCP for AI agents: financing, skills, lending on Base1k Patient Mcp1k patient MCP server
1trippulse1trip PULSE: 21-tool AI travel planner.
3D AI Agent Avatar3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers.89How it compares
MCP-backed planning workspace, not a local agent skill or code-review checker.
FAQ
Who is ai.taskforcehq/taskforce for?
It is for developers and small teams who use AI coding agents and want tasks and plans in Taskforce HQ reachable over MCP.
When should I use ai.taskforcehq/taskforce?
Use it during Build and PM when you are actively implementing features and need the agent aligned to a live task list and plan.
How do I add ai.taskforcehq/taskforce to my agent?
Register the remote streamable-http URL https://mcp.taskforcehq.ai/mcp in your MCP client per the Model Context Protocol registry entry for ai.taskforcehq/taskforce.