Configuration
acf-mcp is configured via environment variables. No secret is ever required: the server holds nothing sensitive. This page lists each variable, its purpose, its default, and the two available transports (stdio and HTTP).
Environment variables
ACF_LOCALEstringdefault: "en"ACF_DOCTRINE_ARCHIVE_URLstringACF_HTTP_PORTintegerdefault: 3000Available transports
Two transports are shipped. stdio is the default, intended for a single user on their own machine. HTTP exists for multi-user deployments behind your own gateway.
Default transport. The client launches the binary on demand via npx and talks JSON-RPC over stdin/stdout. No port, no network setup.
{
"mcpServers": {
"acf": {
"command": "npx",
"args": ["-y", "acf-mcp"],
"env": {
"ACF_LOCALE": "fr"
}
}
}
}Self-hosted doctrine archive
For an air-gapped deployment or one controlled by an internal source of truth, mirror the signed archive and point ACF_DOCTRINE_ARCHIVE_URL at your URL. The signed footer will reflect that mirror, keeping the auditor trace consistent with your infrastructure.
# Point the signed-footer at your self-hosted doctrine mirror
ACF_DOCTRINE_ARCHIVE_URL=https://acf.internal.example.com/doctrine/v1.0/archive.json \
npx -y acf-mcpCLI flags
--transportenumdefault: "stdio"--versionflag--helpflagSee also
- Authentication — HTTP transport, API keys.
- Error codes — behaviour when a variable is invalid or a file is missing.