Keep Ctrl+C ready
The server uses standard input and output. A silent foreground wait is expected when no MCP client is attached.
Reverse the integration direction
armaraos add brings an outside tool into ArmaraOS. armaraos mcp exposes ArmaraOS to another MCP client.
Understand the silent wait
Stdio is a program-to-program pipe. When you launch the server by hand, silence means it is waiting for protocol input.
Read the exact contract
armaraos mcp --help
Launch it live, then exit
armaraos mcpLet a client launch it in real use
An MCP client normally spawns this process and speaks protocol messages over its pipes. Configuring that client is outside this CLI course.
Recognize the same transport elsewhere
The earlier ainl MCP configuration also uses a stdio command. The transport is the same even though the connection direction differs.
Prove the daemon is unaffected
armaraos healthThe verified health check returned healthy and status OK after Ctrl+C.
Check it / enter and leave cleanly
Wait three seconds, then press Ctrl+C.
Follow with a health check and confirm the background daemon remains OK.
A connected MCP client can drive your ArmaraOS agents. Configure only a client you control and review every reachable agent's permissions.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
| Nothing prints | Server is waiting on stdio. | Press Ctrl+C when testing manually. |
| Terminal is occupied | Foreground process owns it. | Open another terminal or exit. |
| Client cannot spawn it | Path or config differs. | Run help from the same environment. |
| Concern after exit | MCP process was separate. | Run health. |