Skip to main content

​
Tool Providers

The Tools Registry is a pluggable system for registering tool providers that agents can call during flow execution. Each provider (IToolProviderConfig) defines:
  • Provider ID — Unique identifier (e.g., tavily, sql, cosmos_internal, exchange, onedrive)
  • Auth configuration — API key, bearer token, or managed identity
  • Variable specs — Rich input forms for tool parameters (same IPromptVariable format as prompts)
  • Output variables — Declared outputs for downstream dot-notation references
  • Custom integrations — REST API, GraphQL, or JavaScript function code
Built-in Tool Providers (seeded via Bootstrap Assets): OBO (On-Behalf-Of) Tools: Exchange and OneDrive tools use delegated Graph API permissions. The user’s token is exchanged server-side via MSAL’s OBO flow, so tools execute as the authenticated user — they can only access the user’s own mailbox, calendar, and OneDrive.

​
MCP Servers

MCP (Model Context Protocol) servers extend agent capabilities through a standardized tool interface. Each registered server (IMCPServerRegistryEntry) specifies: MCP servers are registered in Admin → MCP Servers and can be:
  • Attached to flows via MCP Server nodes in the Flow Designer
  • Attached to chats via enabledMCPServers on the chat configuration
  • Used by the MCP orchestrator when AI_ORCHESTRATOR.MCP is selected on a model endpoint
Built-in MCP Servers (seeded via Bootstrap Assets):
  • Memory — Persistent knowledge graph for agent context
  • Sequential Thinking — Step-by-step reasoning and problem decomposition