Skip to main content
An Agent receives a request, decides what to do, and returns a response. It may answer directly, call one of its own tools, or call a capability from an MCP provider. GroundForge supports two Agent operating models: Both can use Channels, Gateway rules, Operator review, Traces, and Analytics.

Managed Agent

A managed Agent is configured in the GroundForge platform. GroundForge sends the request to the configured model and invokes only capabilities attached through the Agent’s governed setup.

Example

modelcontextprotocol/quickstart-resources

Use the official Weather MCP as the capability source for a managed weather Agent.
  1. Complete Weather MCP Example so GroundForge knows get_alerts and get_forecast.
  2. In Agents, create a managed Agent and choose its model and model credential.
  3. Attach the Weather MCP through an MCP-targeted Gateway.
  4. Publish the Agent and attach a Channel if users should reach it through messaging.
  5. Send a request and open its Trace.
A managed weather request may look like:

External Agent

An external Agent stays in your application. The GroundForge SDK registers it, reports its tools, receives Channel jobs, applies Gateway decisions before a tool runs, and sends Trace events back to GroundForge.

Example

groundforgeai/demo

Run the LangChain weather Agent with automatic input handling or explicit adapters.
Initialize GroundForge after constructing the Agent:
The example does not assume custom caller metadata. The SDK receives the normalized Channel input and passes it to the Agent. Start with LangChain Agent Example, then compare LangChain Agent with Adapters.

Example paths

Use Weather MCP Example for a managed Agent capability source and LangChain Agent Example for an external Agent.
Last modified on July 27, 2026