diff --git a/docs/docs/Components/mcp-client.md b/docs/docs/Components/mcp-client.md
index cd698e731..2c1e3f087 100644
--- a/docs/docs/Components/mcp-client.md
+++ b/docs/docs/Components/mcp-client.md
@@ -9,7 +9,7 @@ import Icon from "@site/src/components/icon";
Langflow integrates with the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) as both an MCP server and an MCP client.
-This page describes how to use Langflow as an MCP client with the [**MCP Tools** component](#use-the-mcp-tools-component) component and your [connected MCP servers](#manage-connected-mcp-servers).
+This page describes how to use Langflow as an MCP client with the [MCP Tools](#use-the-mcp-tools-component) component and the [MCP servers](#manage-connected-mcp-servers) page in **Settings**.
For information about using Langflow as an MCP server, see [Use Langflow as an MCP server](/mcp-server).
diff --git a/docs/docs/Tutorials/agent.md b/docs/docs/Tutorials/agent.md
new file mode 100644
index 000000000..f5d8b7629
--- /dev/null
+++ b/docs/docs/Tutorials/agent.md
@@ -0,0 +1,177 @@
+---
+title: Connect applications to agents
+slug: /agent-tutorial
+---
+
+import Icon from "@site/src/components/icon";
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+This tutorial shows you how to connect a JavaScript application to a Langflow [agent](/agents).
+
+With the agent connected, your application can use any connected tools to retrieve more contextual and timely data without changing any application code. The tools are selected by the agent's internal LLM to solve problems and answer questions.
+
+## Prerequisites
+
+- [A running Langflow instance](/get-started-installation)
+- [A Langflow API key](/configuration-api-keys)
+- [An OpenAI API key](https://platform.openai.com/api-keys)
+- [Langflow JavaScript client installed](/typescript-client)
+
+This tutorial uses an OpenAI LLM. If you want to use a different provider, you need a valid credential for that provider.
+
+## Create an agentic flow
+
+The following steps modify the [**Simple agent**](/simple-agent) template to connect [**Directory**](/components-data#directory) and [**Web search**](/components-data#web-search) components as tools for an **Agent** component.
+The **Directory** component loads all files of a given type from a target directory on your local machine, and the **Web search** component performs a DuckDuckGo search.
+When connected to an **Agent** component as tools, the agent has the option to use these components when handling requests.
+
+1. In Langflow, click **New Flow**, and then select the **Simple agent** template.
+2. Remove the **URL** and **Calculator** tools, and then drag the [**Directory**](/components-data#directory) and [**Web search**](/components-data#web-search) components into your workspace.
+3. In the **Directory** component's **Path** field, enter the directory path and file types that you want to make available to the **Agent** component.
+
+ In this tutorial, the agent needs access to a record of customer purchases, so the directory name is `customer_orders` and the file type is `.csv`. Later in this tutorial, the agent will be prompted to find `email` values in the customer data.
+
+ You can adapt the tutorial to suit your data, or, to follow along with the tutorial, you can download [`customer-orders.csv`](/files/customer_orders/customer_orders.csv) and save it in a `customer_orders` folder on your local machine.
+4. In the [component header menu](/concepts-components#component-menus) for the **Directory** and **Web search** components, enable **Tool Mode** so you can use the components with an agent.
+
+5. For both tool components, connect the **Toolset** port to the Agent component's **Tools** port.
+6. In the **Agent** component, enter your OpenAI API key.
+
+ If you want to use a different provider or model, edit the **Model Provider**, **Model Name**, and **API Key** fields accordingly.
+
+7. To test the flow, click **Playground**, and then ask the LLM a question, such as `Recommend 3 used items for carol.davis@example.com, based on previous orders.`
+
+ Given the example prompt, the LLM would respond with recommendations and web links for items based on previous orders in `customer_orders.csv`.
+
+ The **Playground** prints the agent's chain of thought as it selects tools to use and interacts with functionality provided by those tools.
+ For example, the agent can use the **Directory** component's `as_dataframe` tool to retrieve a [DataFrame](/concepts-objects#dataframe-object), and the **Web search** component's `perform_search` tool to find links to related items.
+
+## Add a prompt component to the flow
+
+In this example, the application sends a customer's email address to the Langflow agent. The agent compares the customer's previous orders within the Directory component, searches the web for used versions of those items, and returns three results.
+
+1. To include the email address as a value in your flow, add a [Prompt](/components-prompts) component to your flow between the **Chat Input** and **Agent**.
+2. In the Prompt component's **Template** field, enter `Recommend 3 used items for {email}, based on previous orders.`
+Adding the `{email}` value in curly braces creates a new input in the **Prompt** component, and the component connected to the `{email}` port is supplying the value for that variable.
+This creates a point for the user's email to enter the flow from your request.
+If you aren't using the `customer_orders.csv` example file, modify the input to search for a value in your dataset.
+
+ At this point your flow has six components. The Chat Input is connected to the Prompt component's `email` input port. Then, the Prompt component's output port is connected to the Agent component's input port. The Directory and Web search components are connected to the Agent's Tools port. Finally, the Agent component's output port is connected to the Chat Output component, which returns the final response to the application.
+
+ 
+
+## Send requests to your flow from a JavaScript application
+
+With your flow operational, connect it to a JavaScript application to use the agent's responses.
+
+1. To construct a JavaScript application to connect to your flow, gather the following information:
+
+ * `LANGFLOW_SERVER_ADDRESS`: Your Langflow server's domain. The default value is `127.0.0.1:7860`. You can get this value from the code snippets on your flow's [**API access** pane](/concepts-publish#api-access).
+ * `FLOW_ID`: Your flow's UUID or custom endpoint name. You can get this value from the code snippets on your flow's [**API access** pane](/concepts-publish#api-access).
+ * `LANGFLOW_API_KEY`: A valid Langflow API key. To create an API key, see [API keys](/configuration-api-keys).
+
+2. Copy the following script into a JavaScript file, and then replace the placeholders with the information you gathered in the previous step.
+If you're using the `customer_orders.csv` example file, you can run this example as-is with the example email address in the code sample.
+If not, modify the `const email = "isabella.rodriguez@example.com"` to search for a value in your dataset.
+
+ ```js
+ import { LangflowClient } from "@datastax/langflow-client";
+
+ const LANGFLOW_SERVER_ADDRESS = 'LANGFLOW_SERVER_ADDRESS';
+ const FLOW_ID = 'FLOW_ID';
+ const LANGFLOW_API_KEY = 'LANGFLOW_API_KEY';
+ const email = "isabella.rodriguez@example.com";
+
+ async function runAgentFlow(): Promise {
+ try {
+ // Initialize the Langflow client
+ const client = new LangflowClient({
+ baseUrl: LANGFLOW_SERVER_ADDRESS,
+ apiKey: LANGFLOW_API_KEY
+ });
+
+ console.log(`Connecting to Langflow server at: ${LANGFLOW_SERVER_ADDRESS} `);
+ console.log(`Flow ID: ${FLOW_ID}`);
+ console.log(`Email: ${email}`);
+
+ // Get the flow instance
+ const flow = client.flow(FLOW_ID);
+
+ // Run the flow with the email as input
+ console.log('\nSending request to agent...');
+ const response = await flow.run(email, {
+ session_id: email // Use email as session ID for context
+ });
+
+ console.log('\n=== Response from Langflow ===');
+ console.log('Session ID:', response.sessionId);
+
+ // Extract URLs from the chat message
+ const chatMessage = response.chatOutputText();
+ console.log('\n=== URLs from Chat Message ===');
+ const messageUrls = chatMessage.match(/https?:\/\/[^\s"')\]]+/g) || [];
+ const cleanMessageUrls = [...new Set(messageUrls)].map(url => url.trim());
+ console.log('URLs from message:');
+ cleanMessageUrls.slice(0, 3).forEach(url => console.log(url));
+
+ } catch (error) {
+ console.error('Error running flow:', error);
+
+ // Provide error messages
+ if (error instanceof Error) {
+ if (error.message.includes('fetch')) {
+ console.error('\nMake sure your Langflow server is running and accessible at:', LANGFLOW_SERVER_ADDRESS);
+ }
+ if (error.message.includes('401') || error.message.includes('403')) {
+ console.error('\nCheck your API key configuration');
+ }
+ if (error.message.includes('404')) {
+ console.error('\nCheck your Flow ID - make sure it exists and is correct');
+ }
+ }
+ }
+ }
+
+ // Run the function
+ console.log('Starting Langflow Agent...\n');
+ runAgentFlow().catch(console.error);
+ ```
+
+3. Save and run the script to send the request and test the flow.
+ Your application receives three URLs for recommended used items based on a customer's previous orders in your local CSV, all without changing any code.
+
+ Response
+
+ The following is an example of a response returned from this tutorial's flow. Due to the nature of LLMs and variations in your inputs, your response might be different.
+
+ ```
+ Starting Langflow Agent...
+
+ Connecting to Langflow server at: http://localhost:7860
+ Flow ID: local-db-search
+ Email: isabella.rodriguez@example.com
+
+ Sending request to agent...
+
+ === Response from Langflow ===
+ Session ID: isabella.rodriguez@example.com
+
+ URLs found:
+ https://www.facebook.com/marketplace/258164108225783/electronics/
+ https://www.facebook.com/marketplace/458332108944152/furniture/
+ https://www.facebook.com/marketplace/613732137493719/kitchen-cabinets/
+ ```
+
+
+
+4. To quickly check traffic to your flow, open the **Playground**.
+ New sessions appear named after the user's email address.
+ Keeping sessions distinct helps the agent maintain context. For more on session IDs, see [Session ID](/session-id).
+
+## Next steps
+
+For more information on building or extending this tutorial, see the following:
+
+* [Model Context Protocol (MCP) servers](/mcp-server)
+* [Langflow deployment overview](/deployment-overview)
\ No newline at end of file
diff --git a/docs/sidebars.js b/docs/sidebars.js
index 5b504ed05..978e95f20 100644
--- a/docs/sidebars.js
+++ b/docs/sidebars.js
@@ -26,6 +26,7 @@ module.exports = {
items: [
"Tutorials/chat-with-rag",
"Tutorials/chat-with-files",
+ "Tutorials/agent",
],
},
],
diff --git a/docs/static/files/customer_orders/customer_orders.csv b/docs/static/files/customer_orders/customer_orders.csv
new file mode 100644
index 000000000..860402a96
--- /dev/null
+++ b/docs/static/files/customer_orders/customer_orders.csv
@@ -0,0 +1,36 @@
+customer_id,customer_email,product_id,product_name,product_category,order_date,order_id
+1,alice.smith@example.com,1,Laptop,Electronics,2024-01-10,1001
+1,alice.smith@example.com,4,Notebook,Stationery,2024-01-15,1002
+1,alice.smith@example.com,6,Wireless Mouse,Electronics,2024-01-28,1003
+1,alice.smith@example.com,8,Desk Lamp,Home,2024-02-05,1004
+2,bob.johnson@example.com,2,Headphones,Electronics,2024-01-12,1005
+2,bob.johnson@example.com,3,Coffee Mug,Home,2024-01-18,1006
+2,bob.johnson@example.com,7,Bluetooth Speaker,Electronics,2024-01-25,1007
+2,bob.johnson@example.com,10,Water Bottle,Sports,2024-02-10,1008
+3,carol.davis@example.com,1,Laptop,Electronics,2024-01-05,1009
+3,carol.davis@example.com,2,Headphones,Electronics,2024-01-20,1010
+3,carol.davis@example.com,5,Backpack,Fashion,2024-01-30,1011
+3,carol.davis@example.com,9,Yoga Mat,Sports,2024-02-15,1012
+4,david.wilson@example.com,3,Coffee Mug,Home,2024-01-08,1013
+4,david.wilson@example.com,4,Notebook,Stationery,2024-01-22,1014
+4,david.wilson@example.com,6,Wireless Mouse,Electronics,2024-02-01,1015
+4,david.wilson@example.com,11,Plant Pot,Home,2024-02-20,1016
+5,emma.brown@example.com,1,Laptop,Electronics,2024-01-14,1017
+5,emma.brown@example.com,3,Coffee Mug,Home,2024-01-25,1018
+5,emma.brown@example.com,5,Backpack,Fashion,2024-02-03,1019
+5,emma.brown@example.com,12,Phone Case,Electronics,2024-02-25,1020
+6,frank.miller@example.com,2,Headphones,Electronics,2024-01-16,1021
+6,frank.miller@example.com,7,Bluetooth Speaker,Electronics,2024-01-28,1022
+6,frank.miller@example.com,10,Water Bottle,Sports,2024-02-08,1023
+7,grace.lee@example.com,4,Notebook,Stationery,2024-01-19,1024
+7,grace.lee@example.com,8,Desk Lamp,Home,2024-02-02,1025
+7,grace.lee@example.com,9,Yoga Mat,Sports,2024-02-18,1026
+8,henry.chen@example.com,1,Laptop,Electronics,2024-01-22,1027
+8,henry.chen@example.com,6,Wireless Mouse,Electronics,2024-02-05,1028
+8,henry.chen@example.com,11,Plant Pot,Home,2024-02-28,1029
+9,isabella.rodriguez@example.com,2,Headphones,Electronics,2024-01-25,1030
+9,isabella.rodriguez@example.com,5,Backpack,Fashion,2024-02-10,1031
+9,isabella.rodriguez@example.com,12,Phone Case,Electronics,2024-02-22,1032
+10,james.taylor@example.com,3,Coffee Mug,Home,2024-01-30,1033
+10,james.taylor@example.com,7,Bluetooth Speaker,Electronics,2024-02-12,1034
+10,james.taylor@example.com,10,Water Bottle,Sports,2024-02-25,1035
\ No newline at end of file
diff --git a/docs/static/img/tutorial-agent-with-directory.png b/docs/static/img/tutorial-agent-with-directory.png
new file mode 100644
index 000000000..a7b022b66
Binary files /dev/null and b/docs/static/img/tutorial-agent-with-directory.png differ