Understand what an MCP provider exposes and how GroundForge discovers and governs it.
An MCP provider is a Model Context Protocol server. It can expose tools, resources, and prompts that an Agent or MCP client can use.GroundForge first runs Discovery to read the provider’s public capability definitions. Those definitions become the inventory you see in the provider page and Gateway editor. Discovery reads names, descriptions, and input schemas; it does not execute the tools.GroundForge supports:
remote MCP providers reached over Streamable HTTP;
local stdio discovery and governed local execution through gforge.
The official Python Weather MCP exposes get_alerts(state) and get_forecast(latitude, longitude).
Weather MCP starts→ GroundForge reads the two tool definitions→ the inventory appears in the MCP provider page→ you select a tool in a Gateway rule→ a governed client or Agent requests the tool→ the decision and result appear in GroundForge
