Follow-up to my earlier post about managing your DevvyBoard from inside your code editor — the MCP integration just grew up a lot. **v0.4.0 is on npm with 19 tools**, and your agent has gone from "can read the board" to genuinely operating the whole product.

**Everything an agent can do now:**

**Kanban** — list projects, read the full board (columns, cards, priorities, deadlines, categories), then create / update / move / delete cards. "Move everything I finished today to Done and bump the deploy card to urgent" is a one-liner in Claude Code.

**Blueprints (new)** — this is the big one. Agents can read your architecture diagrams as a clean text outline, create whole new blueprints, add nodes and connections to existing ones, and **link diagram nodes to kanban cards**. No coordinates needed — the server auto-lays-out everything an agent draws, and a snapshot is taken before every agent edit so you can always one-click revert.

**Ideas** — list the idea backlog, add new ideas, promote an idea straight to a board card.

**Roadmap** — read the public roadmap and publish/unpublish it.

**Chat** — post a message into team chat, so a long-running agent can report "deploy finished, all tests green" where your team actually reads.

**Setup is still one block of JSON:**

    {
      "command": "npx",
      "args": ["-y", "devvyboard-mcp"],
      "env": { "DEVVYBOARD_API_KEY": "dbk_live_YOUR_KEY" }
    }

Works with Claude Code, Cursor, Windsurf — anything that speaks MCP. Keys are scoped and revocable from the dashboard.

My honest test of whether this works: I asked an agent to document DevvyBoard itself. It drew the entire product map (22 nodes, 28 edges) and linked the shipped features to their Done cards — completely over MCP, zero manual drawing.

Full tool docs: https://www.devvyboard.app/docs

What would you automate first if your project board had an API your agent already knew how to use?

🤖 Your AI agent can now draw architecture diagrams, ship roadmaps and post in team chat — DevvyBoard MCP 0.4.0