Dynamic Kanban

Created By
Renato Kuipersa year ago
A dynamic, visual kanban board that lets you collab with Claude, and updates in realtime!
Overview

what is Dynamic Kanban?

Dynamic Kanban is a real-time project management tool that provides a visual kanban board for collaboration with Claude AI, allowing users to manage tasks dynamically and efficiently.

how to use Dynamic Kanban?

To use Dynamic Kanban, install the required dependencies, start the server using the command python3 mcp-kanban-server.py, and open the kanban-board.html in your browser to access the interactive interface.

key features of Dynamic Kanban?

  • Real-time collaboration with bidirectional synchronization between Claude AI and the HTML interface.
  • Dual-mode operation: Autonomous (AI-controlled) and Manual (user-controlled).
  • Drag & drop interface for easy task management.
  • Comprehensive task management capabilities including creation, editing, and deletion of tasks.
  • Robust error handling and data validation using Pydantic models.

use cases of Dynamic Kanban?

  1. Managing software development projects with real-time updates.
  2. Collaborating on tasks with team members using AI assistance.
  3. Tracking project progress and managing task dependencies effectively.

FAQ from Dynamic Kanban?

  • Can I use Dynamic Kanban for any type of project?

Yes! Dynamic Kanban is designed to support various project types including web apps, mobile apps, and more.

  • Is there a setup required before using it?

No setup is required; simply open the kanban-board.html file to start using it immediately.

  • How does the dual-mode operation work?

You can switch between Autonomous mode, where Claude AI controls the board, and Manual mode, where you have full control over task management.

Server Config

{
  "mcpServers": {
    "dynamic-kanban": {
      "command": "python3",
      "args": [
        "./mcp-kanban-server.py"
      ],
      "env": {},
      "description": "Dynamic Kanban MCP Server v3.0 - Real-time project management with WebSocket sync",
      "version": "3.0.0",
      "capabilities": {
        "tools": [
          "create_project",
          "add_feature",
          "configure_board",
          "import_features",
          "kanban_status",
          "kanban_get_ready_tasks",
          "kanban_get_next_task",
          "kanban_move_card",
          "kanban_update_progress",
          "kanban_start_session",
          "kanban_end_session",
          "analyze_task_requirements",
          "validate_dependencies",
          "validate_project_dependencies",
          "get_task_details",
          "clear_kanban",
          "delete_project",
          "remove_feature",
          "remove_features",
          "clear_column",
          "reset_board"
        ],
        "features": [
          "Dynamic project creation for any project type",
          "Real-time UI generation with WebSocket sync",
          "Bidirectional sync between Claude and HTML UI",
          "Feature management with dependencies and circular dependency detection",
          "Pydantic data validation with comprehensive error handling",
          "Board configuration and customization",
          "JSON import/export for data portability",
          "Development session tracking",
          "Task analysis and implementation planning",
          "Drag & drop interface with live updates",
          "Cross-project compatibility",
          "Centralized configuration management",
          "Modular JavaScript architecture"
        ]
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Renato Kuipers
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago