Whatever message this page gives is out now! Go check it out!
MCP server configuration options
Last update:
May 18, 2026
Reference for registering Model Context Protocol (MCP) servers in Adobe ColdFusion Administrator: UI locations, toolbar actions, list columns, and the mcpServers JSON schema for HTTP and STDIO transports.
Purpose
Model Context Protocol (MCP) servers expose tools, prompts, and resources that AI models and AI-enabled features can call at runtime. ColdFusion Administrator lets you centralize MCP server definitions so runtimes can discover capabilities consistently across applications.
MCP Server Configurations page (list)
The main Administrator screen for MCP includes introductory text and a primary heading MCP Server Configurations.
Toolbar actions
| Control | Description |
|---|---|
| Add Server | Starts the flow to create a new MCP server configuration (typically opens the edit experience where JSON is defined). |
| Clear Tools Cache | Refreshes cached tool, prompt, and resource metadata retrieved from configured servers. Use after server-side changes or when diagnostics suggest stale registrations. |
List columns
| Column | Description |
|---|---|
| Actions | Per-row operations such as edit or delete for a configured server entry. |
| Name | Human-readable identifier for the MCP server configuration. |
| Transport | Mechanism used to reach the MCP server (for example HTTP or STDIO), derived from the JSON definition. |
| Connection | Summary of how the server is reached (for example URL for HTTP, or command line for STDIO). |
| Status | Indicates whether the server is currently reachable or active from the Administrator perspective. |
Note: When no servers are configured, the table is empty until you add definitions and save.
Edit MCP Server Configuration page
The edit screen title is Edit MCP Server Configuration. Instructional text states that you edit the JSON configuration for all MCP servers in one place: you can add, modify, or remove server entries.
For HTTP servers, the configuration supports an optional
headers object for custom HTTP headers (for example Authorization or API keys).A collapsible section Sample configurations (reference) provides templates for HTTP and STDIO patterns. Use it as a starting point; replace placeholders with values appropriate for your environment.
Servers Configuration (JSON) field
The primary input is labeled Servers Configuration (JSON) and is required (indicated by an asterisk in the UI).
- Format JSON — reformats the JSON for readability; does not change semantics.
- Placeholder or hint text shown in gray when the field is empty is not persisted; only content you enter and save is stored.
Required root structure
The value must be a JSON object whose top-level key is
mcpServers. Each named entry under mcpServers defines one MCP server.{
"mcpServers": {
"my-http-server": {
"url": "http://localhost:8500/mcp/your-server.cfm",
"headers": {
"Authorization": "Bearer token",
"X-API-Key": "optional"
}
},
"my-stdio-server": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/dir"]
}
}
}Transport types and properties
Use exactly one transport style per server entry: HTTP (remote URL) or STDIO (local process with standard input/output).
| Transport | Keys | Description |
|---|---|---|
| HTTP | url, optional headers | url is the MCP endpoint. Optional headers is an object of string header names to string values (for example bearer tokens or API keys). Do not commit real secrets to source control; use Administrator or secure deployment practices. |
| STDIO | command, args | command is the executable to launch (for example npx). args is an array of command-line arguments passed to that executable. |
Minimal samples (reference)
HTTP server — URL and optional headers:
{
"mcpServers": {
"serverName": {
"url": "http://localhost:8500/mcp/your-server.cfm",
"headers": {
"Authorization": "Bearer token",
"X-API-Key": "optional"
}
}
}
}STDIO server — command and arguments (example uses
npx):{
"mcpServers": {
"serverName": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/dir"]
}
}
}Replace
serverName, URLs, paths, and tokens with your deployment values.Validation and troubleshooting
- Ensure the document is valid JSON before saving (matching braces, double-quoted keys, trailing commas omitted).
- Each server name under
mcpServersmust be unique. - For HTTP, verify the
urlis reachable from the ColdFusion server host and that TLS certificates are trusted when using HTTPS. - For STDIO, verify the executable exists on the server’s
PATHor use absolute paths where supported; confirm arguments match the MCP package documentation. - If tools do not update after a server change, use Clear Tools Cache on the list page, then retest.
Security considerations
- Store bearer tokens and API keys using mechanisms appropriate to your organization; rotate credentials on a schedule.
- Restrict network access to HTTP MCP endpoints with firewalls or private networking where possible.
- STDIO processes run with the privileges of the ColdFusion service account; limit filesystem paths and package sources.
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
|
