Synopsis
fcli ai-assist mcp start-http -c=<configPath> [[-h] [--env-prefix=<prefix>] [--log-file=<logFile>] [--log-level=<logLevel>] [--log-mask=<level>] [--debug]]
Description
Start an HTTP MCP server exposing only exported functions from imported action YAML files defined in a config file. Generate a sample config file with 'fcli ai-assist mcp create-http-config --type <ssc|fod>' and customize the generated YAML for your environment. The server listens for MCP POST requests on the /mcp endpoint. Each request must include the product-specific auth header as semicolon-separated key=value pairs; escape literal '\', ';', or '=' characters as '\\', '\;', or '\='.
|
Note
|
For better user experience and potentially lower token usage, consider Fortify skills from https://github.com/fortify/skills, which can be installed through your AI assistant marketplace (if available) or by utilizing the `fcli ai-assist extensions' commands. |
|
Note
|
The HTTP MCP server exposes a larger attack surface than local stdio MCP server; use HTTP MCP server only when needed and prefer HTTPS with properly configured certificates. |
AUTH HEADERS (per HTTP request): - SSC mode: X-AUTH-SSC: token=<sscToken>[;sc-sast-token=<scSastClientAuthToken>] - FoD mode, user/PAT auth: X-AUTH-FOD: tenant=<tenant>;user=<user>;pat=<pat> - FoD mode, client auth: X-AUTH-FOD: client-id=<clientId>;client-secret=<clientSecret> Exactly one FoD auth mode must be specified per request.
Options
- -c, --config=<configPath>
-
Path to HTTP MCP YAML config file. Generate a template with 'fcli ai-assist mcp create-http-config'.
Generic fcli options (also see documentation link below)
- --debug
-
Enable collection of debug logs.
- --env-prefix=<prefix>
-
Prefix for resolving default option values. Default value: FCLI_DEFAULT.
- -h, --help
-
Use 'fcli [command] -h' to display help for fcli (sub-)commands.
- --log-file=<logFile>
-
Write log output to file. Default: ./fcli.log if logging is enabled.
- --log-level=<logLevel>
-
Set logging level: TRACE, DEBUG, INFO, WARN, ERROR, NONE.
- --log-mask=<level>
-
Log mask level: high, medium, low, none. Default: medium. Masking is done on a best-effort basis; no guarantee that all sensitive data will be masked.