MCP

The Model Context Protocol lets an agent call tools that live on a remote server. Coresource supports two arrangements, and the difference is who runs the MCP client.

Hosted connectionLocal server
Client runs onCoresourceYour process
Credential held byCoresource, encryptedYour process
Survives your process exitingYesNo
Can reach your private networkNoYes
Configured withmcpServersregisterMcpServer()

Hosted connections keep credentials out of your process and survive it exiting, which makes them right for third-party SaaS. Local registration is right when the server can only be reached from inside your network.

MCP is configured on agent and saga types; it does not apply to one-shot.