Skip to main content

MCP: More Items Operations

Release Notes | July 7th, 2026

Written by Zvi Cohen Zion

Key Takeaways

  • Bulk Operations: Bulk creates and updates work items, feedback items, and feedback connections in a single call.

  • Read and Add Comments: AI agents can read the discussion on work or feedback items and leave comments of their own.

  • Map Dependencies: AI agents can create and edit blocks, blocked-by, and related relationships.

  • Manage Portfolio Items: Create and update initiatives and portfolio OKRs, and link work items to them.

  • Feedback Custom Fields: Read, filter, update and bulk update the new workspace feedback custom fields on your feedback items.


Bulk Operations

Until now, every write through the Craft.io MCP handled a single item per call. If your agent finished a sprint planning pass or generated thirty stories from a PRD, it had to loop through thirty separate calls - slow, token-hungry, and fragile when one call in the middle failed.

Bulk operations change that. Agents can now create items, update items, update feedback, and manage feedback connections in batches - passing an array of records in one call. Ask your AI assistant to re-prioritize the backlog or ingest a quarter's worth of analyzed feedback, and the whole change lands in one operation. The result is faster agent workflows that cost less to run, and a real ingestion path for AI-driven work at scale.


Read and Add Comments

Comments are where the reasoning behind an item lives - but until now, the MCP couldn't see them. Agents worked from titles and descriptions alone, and when they took an action there was nowhere for them to explain why. With this update, agents can leave notes and evidence on the items they touched. Your AI tools can now read the full comment thread on work items and feedback items, and add comments of their own, including internal notes on feedback items. An agent that triages feedback can now document its rationale right on the item, and an agent drafting a spec can take the team's discussion into account.


Map Dependencies

Dependencies could be read through the MCP, but not created or changed. When an agent analyzing your delivery plan spotted that one epic blocks another, all it could do was tell you - you still had to open Craft.io and wire up the relationship yourself. Agents can now create dependencies between items and update the relationship type - blocks, blocked by, or related to. Ask your AI to scan the quarter's plan for hidden blockers, and it can record every relationship it finds directly in Craft.io.


Manage Portfolio Items

Strategy work stopped at the workspace boundary. Agents could read portfolio initiatives and OKRs but couldn't create or update them, so any portfolio-level change meant switching back to manual editing. The MCP now supports creating and updating portfolio items - initiatives, objectives, and key results - with the same fields you can edit in the Craft.io UI. Work items can be linked to both workspace and portfolio OKRs, so an agent can align an entire quarter's plan to strategy in one pass, from the epic level up to the portfolio level.


Feedback Custom Fields

Your feedback items carry the new feedback custom fields - segments, revenue impact, sentiment - but the MCP did not return them. Now, feedback custom fields are fully available: agents can read them, filter feedback by them, and even bulk update them. This means that now you can create a new Feedback custom field, for example for feedback sentiment and let your agent analyze the feedback description and update the sentiment value for each feedback. Another example could be if you want to move formal values from the labels field to a new feedback custom field. Just let your agent move all values to the new field.

Did this answer your question?