foundry-toolbox

Connect agents to Microsoft Foundry Toolboxes via a Streamable HTTP MCP endpoint.

5|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/aiappsgbb/awesome-gbb --skill foundry-toolbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundry-toolbox
Source: https://github.com/aiappsgbb/awesome-gbb/tree/main/skills/foundry-toolbox
Command: npx skills add https://github.com/aiappsgbb/awesome-gbb --skill foundry-toolbox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The foundry-toolbox Skill solves the challenge of wiring multiple Microsoft Foundry tools into an agent without duplicating credentials, authentication logic, and version management across each tool.

Core Features & Use Cases

  • Single MCP endpoint, centralized tool bundle: Exposes a managed multi-tool bundle (MCP servers, web search, Azure AI Search, code interpreter, file search, OpenAPI, and agent-to-agent calls) behind one endpoint so agents connect to one URL.
  • Versioned toolbox deployments: Supports default and version-pinned endpoints to help you test safely and promote versions deliberately.
  • Hosted-agent integration patterns with guardrails: Documents how to consume the toolbox from code-based agents (MAF, LangGraph, and GitHub Copilot SDK) and explicitly prevents common failure modes like unauthorized/toolbox calls or missing preview headers.

Quick Start

Use the foundry-toolbox Skill to connect a code-based agent to the hosted toolbox MCP endpoint and let the platform handle credentials and versioning for a multi-tool workflow.

Frequently Asked Questions about foundry-toolbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect an agent to multiple Microsoft Foundry tools through a single MCP endpoint?

You can connect a code-based agent to multiple Microsoft Foundry tools by using a single Streamable HTTP MCP endpoint that bundles web search, Azure AI Search, code interpreter, and OpenAPI tools together. This centralized approach eliminates the need to wire each tool individually.

Why do my Microsoft Foundry toolbox calls fail with unauthorized errors from my agent?

Unauthorized toolbox calls typically occur when the mandatory preview opt-in header Foundry-Features: Toolboxes=V1Preview is missing or the AAD token scope is handled incorrectly. You must include this specific header and ensure correct token injection for successful authentication.

Can I use Microsoft Foundry toolboxes with LangGraph or GitHub Copilot SDK agents?

Yes, the hosted Microsoft Foundry toolbox MCP endpoint supports integration with code-based agent architectures including LangGraph, GitHub Copilot SDK, and MAF. The platform provides specific integration patterns and guardrails to prevent common failure modes for these frameworks.

What is centralized credential injection for MCP tool bundles and when do I need it?

Centralized credential injection is the process of managing authentication tokens and refresh logic in one place for a bundle of MCP tools. You need this when wiring multiple Microsoft Foundry tools into an agent to avoid duplicating authentication code across each individual tool.

Does the Foundry MCP endpoint support standard MCP ping and prompts list operations?

No, the Microsoft Foundry toolbox MCP endpoint explicitly skips unsupported MCP operations like ping and prompts list. You must use streaming tool calls instead and adhere to these connector-specific constraints to avoid errors during agent workflows.

What is the best way to manage versioning for Microsoft Foundry toolboxes in production?

The best way to manage versioning is to use the default and version-pinned endpoints provided by the Foundry toolbox. This allows you to test new versions safely and promote them deliberately without breaking existing agent integrations.