Skip to content

Commit e4e241b

Browse files
vfanelleValerie Fanelle
andauthored
Updating title of MCP Gateway QuickStart (#608)
Co-authored-by: Valerie Fanelle <valeriefanelle@mac.local.meter>
1 parent a16b64e commit e4e241b

File tree

1 file changed

+2
-2
lines changed
  • app/en/home/mcp-gateway-quickstart

1 file changed

+2
-2
lines changed

app/en/home/mcp-gateway-quickstart/page.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Call a tool in your IDE/MCP Client"
3-
description: "Learn how to call tools in 3rd party agents, apps, or IDEs"
3+
description: "Learn how to call a tool in your IDE/MCP Client"
44
---
55

66
import { Steps, Tabs, Callout } from "nextra/components";
@@ -21,7 +21,7 @@ export const MCP_GATEWAY_URL_DARK_HEIGHT = 506;
2121
export const MCP_GATEWAY_URL_LIGHT_WIDTH = 2406;
2222
export const MCP_GATEWAY_URL_LIGHT_HEIGHT = 506;
2323

24-
# Calling tools in 3rd party agents, apps, or IDEs with Arcade
24+
# Call a tool in your IDE/MCP Client
2525

2626
Tools enable your AI agents to perform actions on your behalf. For specific workflows and use cases, this may involve calling tools from multiple MCP servers. Arcade facilitates this by allowing you to create MCP Gateways to federate the tools from multiple MCP servers into a single collection for easier management, control, and access. For example, if your agent specializes in solving specific tickets in Linear, you may want to use tools from the GitHub, Slack and Linear servers in your agent. These add up to 88 tools, which could be overwhelming for an LLM to use effectively. What you want is to get from these servers only the tools that matter for your agent. An MCP Gateway allows you to do just that: pick only the tools required for this workflow, and you can connect it to any MCP client, making it easy to port your agent to multiple platforms and IDEs, and even share it with other users.
2727

0 commit comments

Comments
 (0)