Configuration
Configure the MCP transport, backend destination, and privacy settings for your agent.
MCP over stdio
Emfirge is a local process launched by your MCP client. It communicates with the client over stdio and sends HTTP requests to the configured backend. Use the following server entry in a client that accepts JSON MCP configuration.
{
"mcpServers": {
"emfirge": {
"command": "npx",
"args": ["-y", "@emfirge/mcp"],
"env": { "EMFIRGE_PRIVACY": "strict" }
}
}
}
Codex configuration
The Emfirge installer writes this TOML block for Codex. Merge it with your existing configuration rather than replacing the whole file.
[mcp_servers.emfirge]
command = "npx"
args = ["-y", "@emfirge/mcp"]
[mcp_servers.emfirge.env]
EMFIRGE_PRIVACY = "strict"
Environment variables
| Variable | Purpose |
|---|---|
| EMFIRGE_BASE_URL | Backend API URL; defaults to https://emfirge.cloud/api |
| EMFIRGE_PRIVACY | strict (default), balanced, or off |
| EMFIRGE_TRUSTED_ACCOUNT_ID | Trusted AWS account used by setup help |
| EMFIRGE_EXTERNAL_ID | STS ExternalId; default aws-risk-agent |
| EMFIRGE_TEMPLATE_URL | CloudFormation template URL used by setup help |
Use your own backend
Set EMFIRGE_BASE_URL in the MCP server environment to your backend’s API URL. Configure the role trust and ExternalId for that backend. A custom URL does not install or start an engine for you.
Keep the MCP tool set and backend routes compatible. If branch tools are absent, use a matching build of the client and engine.
"env": {
"EMFIRGE_BASE_URL": "https://your-emfirge-host.example/api",
"EMFIRGE_PRIVACY": "strict"
}
Inspect local setup
The status command reports configured clients and privacy settings. Confirm that your agent can list Emfirge tools to verify the connection.
npx @emfirge/mcp status