Whatever message this page gives is out now! Go check it out!
Transport configuration
Last update:
May 18, 2026
Learn how transport settings define communication between an MCP client and server in ColdFusion.
Transports define how the client talks to the server. MCP supports several transports at the spec level; ColdFusion MCP focuses on:
- HTTP (remote or local over HTTP)
- STDIO (local subprocess)
Each has different trade-offs around deployment, security, and performance.
HTTP transport
HTTP transports are best when:
- The MCP server is remote and shared (for example, an MCP in an internal environment or a public MCP).
- You want standard observability and network-level controls.
- You’re exposing a CF MCP server to multiple clients.
For example,
<cfscript>
configData = {
transport: {
type: "http",
url: "https://remote.mcpservers.org/fetch/mcp"
},
clientInfo: {
name: "http-client",
version: "1.0.0"
},
requestTimeout: 30
};
mcpClient = MCPClient(configData)
</cfscript>
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
type | String | Yes | Must be "http" |
url | String | Yes | MCP endpoint URL (HTTP/HTTPS) |
We're glad. Tell us how this page helped.
We're sorry. Can you tell us what didn't work for you?
Share additional feedback to help us improve.
0/255
|
