Whatever message this page gives is out now! Go check it out!
Client capabilities
Last update:
May 18, 2026
Understand how client capabilities influence server behavior in an MCP integration.
Overview
Client capabilities define which optional features your MCP client supports. These capabilities influence how the MCP server interacts with your client.
When you enable a capability, you are signaling to the server that your client is prepared to handle specific types of requests.
Common capability flags
The following capability flags are commonly used in ColdFusion MCP clients:
sampling– Indicates whether the client can handle sampling requests (LLM calls).roots– Indicates whether the client will manage resource roots for scoping.elicitation– Indicates whether the client can collect additional user input when requested by the server.
Example configuration
<cfscript>
configData = {
transport: { /* transport config */ },
capabilities: {
sampling: true, // Enable sampling requests
roots: true, // Enable root resource management
elicitation: true // Enable user input requests
}
};
</cfscript>
Gradual enablement strategy
You do not need to enable all capabilities at once.
For example, you can start with:
sampling = falseroots = falseelicitation = false
Then enable each capability only after implementing the corresponding consumer handler.
This incremental approach helps you:
- Reduce integration complexity
- Avoid unsupported server requests
- Gradually adopt advanced MCP workflows
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
|
