MCP Server Design Question: Should Tool Metadata Be Internal Config or an Exposed Resource?
Sea-Letterhead-9529 · reddit · 2026-09-10
A developer building an MCP server for their organization has an architecture question: one Tool needs a structured metadata definition to operate, currently stored as a static JSON file inside the app. While primarily consumed by that Tool, exposing the metadata as an MCP Resource is also a requirement.
They weigh two options: keep the metadata as internal application config accessed directly by the Tool, or expose it as an MCP Resource that the Tool (and potentially clients) access through the MCP Resource model. They want guidance on MCP best practices and architectural trade-offs rather than implementation details.
More from coding & agent
- AgentGrad Targets the Right Agent First: Intervention-Guided Prompt Optimization for Multi-Agent Systems — Jaewon Chu · 2026-09-10
- TUM's PlannerForge Uses LLM Agents to Automate Scenario-Based Testing of Autonomous Driving Motion Planners — TUM-AVS · 2026-09-10
- Google's free Agents Companion ebook is out for download — CodeByPoonam · 2026-09-10
- Anthropic's prompt engineering docs: when to prompt-engineer and where to start — CodeByPoonam · 2026-09-10
- Anthropic's Building Effective Agents: simple composable patterns beat complex frameworks — CodeByPoonam · 2026-09-10
- OpenAI's practical guide to building agents, plus a playbook for scaling AI use cases — CodeByPoonam · 2026-09-10