New fields should be added to the _meta field
Open
Nobody has claimed this yet.
coaz
- Dominant language
- TypeScript
- Stars
- 160
- Forks
- 40
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 23
Description
From @maxwellgerber:
MCP extensions like UI hang their values off of the _meta field, not on top-level objects - https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/2026-01-26/apps.mdx - I know there is a tool annotations IG that is taking a look at this but unsure what the current recommendation is
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked MCP Apps specification and the issue's reference to the tool annotations IG. Confirm the current recommendation for placing these values, identify which new fields are required, and document the exact schema change needed before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100