Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions changelog/2025-10-21-mcp-tools-ai-agents/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
---
slug: mcp-tools-ai-agents
version: v1.586.0
title: MCP Tools for AI Agents
tags: ['AI Agents', 'MCP', 'Tools']
description: AI Agents can now connect to MCP servers, enabling them to execute any tool made available by the MCP server.
features:
[
'Connect MCP servers to AI Agents ',
]
docs: /docs/core_concepts/ai_agents
---
24 changes: 20 additions & 4 deletions docs/core_concepts/54_ai_agents/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -24,17 +24,33 @@ Select or create an AI resource that contains your API credentials and endpoint

Choose the specific model you want to use from your selected provider. Available models depend on your chosen provider and resource configuration.

## Tools
## Script tools

AI Agents can be equipped with tools that extend their capabilities beyond text and image generation. Tools are Windmill [scripts](../../script_editor/index.mdx) that the AI can call to perform specific actions or retrieve information. You can add tools from three sources:
AI Agents can be equipped with script tools that extend their capabilities beyond text and image generation. Tools are Windmill [scripts](../../script_editor/index.mdx) that the AI can call to perform specific actions or retrieve information. You can add tools from three sources:

- **Inline scripts** - Write custom tools directly within the flow
- **Workspace scripts** - Use existing scripts from your Windmill workspace
- **Hub scripts** - Leverage pre-built tools from the Windmill Hub

Each tool must have a unique name within the AI agent step and contain only letters, numbers, and underscores. It should be descriptive of the tool's function to help the AI understand when to use them.
Each script tool must have a unique name within the AI agent step and contain only letters, numbers, and underscores. It should be descriptive of the tool's function to help the AI understand when to use them.

When tools are configured, the AI agent can decide when and how to use them based on the user's request. It selects the most appropriate tool by name, and issues a tool call with JSON arguments that conform to the tool’s input schema. Windmill executes the underlying `script` and returns a JSON result, which is surfaced back to the model as a tool response message and is included in `messages`.
When script tools are configured, the AI agent can decide when and how to use them based on the user's request. It selects the most appropriate tool by name, and issues a tool call with JSON arguments that conform to the tool's input schema. Windmill executes the underlying `script` and returns a JSON result, which is surfaced back to the model as a tool response message and is included in `messages`.

### MCP tools

AI Agents can connect to [MCP (Model Context Protocol)](../51_mcp/index.mdx) servers as tools, enabling access to any tools exposed by MCP-compatible servers. To use MCP tools:

1. Create an MCP resource in Windmill with:
- **Name**: Identifier for the MCP resource
- **URL**: The MCP server endpoint URL
- **Auth token** (optional): Authentication token for the MCP server
- **Headers** (optional): Additional HTTP headers for the connection

2. Add the MCP resource to your AI Agent step as a tool

3. The AI agent will automatically discover and use tools exposed by the MCP server

**Note**: Only HTTP streamable MCP servers are supported.

## Input parameters

Expand Down