Repository navigation
[FEATURE]: Support _meta when calling downstream MCP tools #17084
Description
When opencode receives a tools/call request that contains _meta, that metadata does not appear to be forwarded when opencode invokes downstream MCP tools.
In a typical setup:
UI → opencode → downstream MCP server
the UI may attach runtime metadata in _meta (for example document IDs, container IDs, workspace context, or tracing information). This metadata is intended to travel with the request but remain hidden from the LLM.
Currently, when opencode makes the downstream tools/call, the _meta field is dropped. As a result, downstream MCP servers lose request-scoped context.
Example incoming request:
{
"method": "tools/call",
"params": {
"name": "docuai_agent_tool",
"arguments": {
"user_request": {
"user_input": "Translate this document to French"
}
},
"_meta": {
"com.example/documentId": "doc_123",
"com.example/containerId": "cont_456"
}
}
}Expected downstream request:
{
"method": "tools/call",
"params": {
"name": "translate_document_preserving_structure",
"arguments": {
"destinationLanguageThreeLetterCode": "fra"
},
"_meta": {
"com.example/documentId": "doc_123",
"com.example/containerId": "cont_456"
}
}
}Forwarding _meta would allow downstream MCP tools to access request context (e.g., document IDs or workspace metadata) without exposing those values to the model.
It would be helpful if opencode preserved _meta from incoming requests and forwarded it to downstream tools/call requests when present.
Activity
github-actions commentedon Mar 11, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
[-][FEATURE]: Forward request-scoped MCP _meta from incoming opencode requests to downstream MCP tool calls[/-][+][FEATURE]: Support _meta when calling downstream MCP tools[/+]github-actions commentedon Mar 11, 2026
Thank you for updating the issue — the description is clear and well-written.
However, the issue still doesn't fully match our Feature Request template. One required field is missing:
You can do this by editing the issue and selecting the Feature Request template, or by adding the checkbox manually:
Please update the issue to address this.
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.