Skip to content

Commit 3af7e78

Browse files
committed
add transport modes to glossary
1 parent 0771075 commit 3af7e78

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

‎app/en/home/glossary/page.mdx‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,16 @@ Understand why [LLMs usually perform poorly](/home/use-tools/types-of-tools#why-
5151

5252
_Learn more about [tool context](/home/build-tools/tool-context)._
5353

54+
### Transport Modes
55+
56+
MCP servers can communicate with clients through different transport mechanisms. Each transport is optimized for specific use cases and client types.
57+
58+
The stdio (standard input/output) transport is used for direct client connections. It is ideal for desktop applications (Claude, VS Code, Cursor) and command-line tools.
59+
60+
The HTTP transport provides REST/SSE endpoints for web-based clients. It is the default transport mode and is used for most clients.
61+
62+
_Learn more about [transport modes in the MCP Protocol documentation](https://modelcontextprotocol.info/docs/concepts/transports/)._
63+
5464
### MCP (Model Context Protocol)
5565

5666
MCP is an open standard protocol that enables LLMs to access and use tools and data sources. Arcade tools go further than MCP with enterprise-grade authentication, secure token management, and fine-grained permissions. This allows your tools to be accessible to any LLM that supports MCP, while maintaining security and user privacy.

0 commit comments

Comments
 (0)