AKADATA LIMITED
AKAMAN Configuration
AKAMAN stdio operation needs no configuration; the optional HTTP transport uses /etc/akaman/akamcp.conf with a bearer key and binds 127.0.0.1:8931 by default.
AKAMAN
A small Linux C utility that retrieves the compact documentation fragment an AI agent needs from the host where it is running.
Configuration: stdio by default, optional authenticated HTTP
AKAMAN has two distinct operating modes. The distinction matters because only one of them requires any configuration file at all.
Local CLI and stdio MCP
Normal local command-line use, and akaman --mcp for an agent on the same machine, need no HTTP bearer key and no configuration file. The transport is stdio: the client launches the binary and communicates with it over its standard input and output. This is the default integration path for Codex and OpenCode.
HTTP / webMCP
The optional HTTP server (--http or --web) speaks JSON-RPC 2.0 over HTTP and authenticates with a bearer key. It reads that key from:
/etc/akaman/akamcp.confunless another path is selected with --conf PATH. The file format is minimal: a single APIKEY= assignment. Blank lines and lines beginning with # are ignored. Use a placeholder only — never a real credential:
# /etc/akaman/akamcp.conf
APIKEY=replace-with-a-long-random-secretThe server binds to 127.0.0.1:8931 by default and refuses to start without an APIKEY. Remote HTTP exposure is optional and should be deliberate: bind outward (for example --http=0.0.0.0:8931) only behind a TLS-terminating proxy or a trusted network, since the transport itself is plain HTTP with a bearer token.
Accurate distinction
AKAMAN’s normal local operation requires no cloud or network service. It also provides an optional authenticated HTTP transport for network clients. Saying “AKAMAN has no network” would be inaccurate once HTTP is enabled; the correct statement is that network access is not required for local use and is opt-in.