Servers
@create mcp is one form and three transports.
| Transport | You provide |
|---|---|
| HTTP | The endpoint. No credentials, or an optional OAuth client id for servers that do not register clients |
| Azure client credentials | Tenant id, client id, client secret, scope |
| stdio | Command, arguments, working directory, and env |
When Settings has environments or customers, the form asks for those too. A new server starts on the header choice. Changing only the environment or the customer does not require another test after the current values have already passed.
Test connection must succeed before Save. An HTTP server that answers 401 is not a form error. The test passes with “asks for OAuth sign-in”. Connecting or calling then says Run @mcp signin <server>.
mock://local tests and saves offline, with canned echo and ping tools.
Connect this tab
@connect
@connect Docs@connect connects the current tab and keeps any MCP servers already open on that tab. Other tabs keep their own servers. After a restart the tab remembers the names and shows off until you connect again, unless Connect when the app starts is ticked.
That tick box is in the server editor, off by default, stored as auto_connect. On launch the app connects those servers on the first tab in the background. The scrollback gets one MCP auto-connected line. Servers that fail are named in a quiet notice. A server that needs sign-in says to run @mcp signin <server>. No browser opens at start-up.
The status strip lists connected servers as pills. Hover a pill and confirm Disconnect? to drop that one. Esc cancels.
List, edit, export
@mcp
@servers@mcp and @servers are the same list. You can edit, duplicate, or delete. A blank secret on edit keeps the stored one. Tick rows to export a .aitmcp file, or import one. Import asks before replacing a server of the same name.
.aitmcp is encrypted (Argon2id, AES-256-GCM) and is MCP only. It stores each server’s environment id and customer id. The names and colours stay in Settings. The export password is at least 12 characters and is not stored.
Secrets (the Azure client secret, and stdio env values whose names look like secrets) go to the OS keychain. They are not written to yaml, the connections file, the scrollback, or the logs.
Stdio framing
Stdio servers speak newline-delimited JSON-RPC: one compact JSON message per line. Replies from older servers that use Content-Length headers are still read. Stray non-JSON lines on stdout are skipped.
What termorq-cli does with a server
termorq-cli mcp lists saved servers and does not connect. termorq-cli tools <connection> connects and lists that server’s tools. termorq-cli run of a collection skips tool steps. termorq-cli run --file can call tools, one MCP session per server, and a destructive tool needs --yes. Run a collection has the commands.
termorq-cli mcp --workspace ~/src/acme-apis
termorq-cli tools Docs --data-dir ~/Library/Application\ Support/com.garrardkitchen.ai-terminalOn Linux the data folder is ~/.local/share/com.garrardkitchen.ai-terminal. On Windows it is %APPDATA%\com.garrardkitchen.ai-terminal. termorq-cli models and termorq-cli tools read that folder. They reject --workspace.