Spaces:
Running
Running
[Discussion] Building the Hugging Face MCP Server
#26
by evalstate - opened
This is for discussion of the blog post https://huggingface.co/blog/building-hf-mcp. Let us know your thoughts or questions!
One thing I would love to see in the HF MCP server story is a small convention for preserving tool-call metadata across hosts.
The practical fields I keep wanting when debugging MCP-backed agents are:
- run/session id
- user turn id
- tool call id
- host/client name + version
- selected MCP server/tool
- input/output metadata
- retry/timeout state
- final artifact or action
That does not all need to be part of the MCP server itself, but having examples that show where the host should store it would help a lot. We are exploring this from the local/self-hosted control-plane side in Armorer: https://github.com/ArmorerLabs/Armorer