Answer: Pi has no Crew MCP surface and cannot forward the MCP server array, so another backend should be chosen when Crew memory, scheduling, subagent, or other MCP tools are needed. OpenCode applies server-level filtering, withholding an entire Crew MCP server if any of its tools is disabled, while compaction is supported on both Codex and OpenCode sessions. Status: Confirmed Entry: tool/kiro/features/backend-capability-differences Revision: 1 Digest: sha256:241587357f6bca82 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:38:32Z Last changed: 2026-11-13T03:38:32Z Last verified: 2026-11-20T13:23:09Z Next check: 2026-11-21T13:23:09Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Pi MCP limitation | Pi has no Crew MCP surface | [1] | 2026-11-20 Pi MCP forwarding | pi-acp does not forward the MCP server array | [1] | 2026-11-20 OpenCode filtering | OpenCode applies server-level filtering | [1] | 2026-11-20 OpenCode partial tool set | Crew withholds that whole server from the OpenCode session rather than presenting a partial tool set | [1] | 2026-11-20 Compaction support | Compaction is supported on both Codex and OpenCode sessions | [1] | 2026-11-20 Cross-backend features | Monitor controls, project changes, follow-up cards, and conversation reset work across all backends | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Agent backends - Features - Crew - Docs - Kiro". https://kiro.dev/docs/crew/features/agent-backends/ Role: primary. Accessed: 2026-11-20T13:23:09Z Quote: "Pi has no Crew MCP surface." (Supports: Pi MCP limitation) Quote: "pi-acp does not forward the MCP server array" (Supports: Pi MCP forwarding) Quote: "OpenCode applies server-level filtering." (Supports: OpenCode filtering) Quote: "Crew withholds that whole server from the OpenCode session rather than presenting a partial tool set" (Supports: OpenCode partial tool set) Quote: "Compaction is supported on both Codex and OpenCode sessions." (Supports: Compaction support) Quote: "Monitor controls, project changes, follow-up cards, and conversation reset work across all backends" (Supports: Cross-backend features) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: da86ffb9ebc7c9ffb32871427dc8df736d2641c895e7695ab46d5e773da2478d (captured 2026-11-20T13:23:06Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:23:09Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:23:09Z Last attempt: 2026-11-20T13:23:09Z Notes and limitations: Extracted automatically from a single official source (section "Capability differences"). Related: https://latestn.com/tool/kiro/features/bugfix-spec-workflow How does the Kiro bugfix spec workflow work across the analysis, design, and tasks phases? https://latestn.com/tool/kiro/features/bugfix-specs-benefits What are bugfix specs in Kiro and what benefits do they provide? https://latestn.com/tool/kiro/features/built-in-tool-catalog Which built-in tools does Kiro have and where are they available? https://latestn.com/tool/kiro/features/annotate-page How do I annotate a page in the Kiro Crew Browser panel? https://latestn.com/tool/kiro/features/artifact-supported-content What types of content can Kiro agent artifacts contain? https://latestn.com/tool/kiro/features/ask-kiro-to-read-image How do I ask Kiro to read an image file? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:38:32Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/features/backend-capability-differences/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/features/backend-capability-differences POST: https://latestn.com/dispute/tool/kiro/features/backend-capability-differences with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/features/backend-capability-differences?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the capability differences between Kiro Crew agent backends? Revision 1, last verified 2026-11-20T13:23:09Z. https://latestn.com/tool/kiro/features/backend-capability-differences (accessed 2026-11-21T09:53:14Z). @misc{LatestN_tool_kiro_features_backend_capability_differences_r1, title = {What are the capability differences between Kiro Crew agent backends?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/features/backend-capability-differences}}, note = {Revision 1; digest sha256:241587357f6bca82; last verified 2026-11-20T13:23:09Z; accessed 2026-11-21T09:53:14Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/features/backend-capability-differences