MCP request meta data to MCP server
Resolved 💬 3 comments Opened Dec 12, 2025 by yitoli-c Closed Jan 31, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What feature would you like to see?
As MCP server developer, it would be nice to know which agent have requested the MCP tool.
By looking at a tool call request context from MCP server, we see:
Copilot in vscode, does send some meta data to MCP server:
RequestContext(
...,
meta=Meta(
progressToken='1106ae9e-bd94-46ef-a2c5-d26891770c41',
vscode.conversationId='dc30885e-3edb-4744-8521-a8e63f890573',
vscode.requestId='bf766dd8-b330-4d1d-bac5-8bfa3f71b8dc'
),
...
) Codex (CLI/vscode extension) doesn't send any meta data to MCP server:
RequestContext(
...,
meta=Meta(progressToken=3),
...
) so no way of telling which Agent have requested the tool call.
MCP spec on meta data still seem quite open:
https://modelcontextprotocol.io/specification/2025-11-25/basic/index#meta
It would be nice for codex MCP client to send some meta data indicating the tool call requests come from codex agent, so as the MCP server developer, I can distinguish tool calls used by different Agents.
Additional information
_No response_
3 Comments
Can you expand on what information you're looking for? When you say "agent", are you referring to the agent harness (as in "codex")? Or the model (as in "gpt-5.1-codex-max")? Or the session ID?
What use case do you have in mind here? What would the MCP server do with this information?
"agent" harness (codex/copilot/cursor etc.).
As MCP server developer, it's nice to know the consumer group (which Agent) of the MCP tools provided.
This feature request has not received any upvotes in the past two months, so I'm going to close it.