[itaides]

Design proposal

Proposal: proposals/mcp-references.md

This adds an optional references argument to the MCP tools content_create and content_update, with the same shape and meaning as the REST API's. Since 1.0 a reference field bound to a relation can only be set through references, and the REST handlers already take it, but the MCP tools never pass it on. So an agent writing through MCP can fill every field except a relation, and a person has to finish each entry in the admin.

It's the MCP half of Discussion #3598; #4100 covers the listing half. I've written it as a feature plan because the change is additive and stays inside the existing handlers. If you'd rather treat the MCP tool schema as a public-API RFC trigger, I'll move it to the RFC template.

Proposal type

• Feature plan
• RFC
• Amendment, supersession, or withdrawal

Related work

Discussion: #3598 · design PR #4100 (references in collection listings)

Readiness

• The proposal identifies its author and, for an RFC, its champion and Maintainer sponsor
• The proposal describes observable behavior, compatibility, failure handling, and verification in proportion to its risk
• Conflicting accepted or pending proposals are reconciled in this pull request
• This pull request contains no implementation code
• The proposal status is accepted (check only when ready to merge)

[changeset-bot]

⚠️ No Changeset found

Latest commit: a29f784

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR