MCP & CLI
Eight focused answers about mcp & cli, with links to the full guides.
Eight focused answers about mcp & cli, with links to the full guides.
Is there an era login command?
No. The current CLI has no persistent era login flow. Era Desktop prepares the chat-session environment; run the command in that engine’s terminal. Source execution also requires an existing session URL and token; an MCP key is not a CLI session.
Why can my terminal not find era?
Era writes the command into the chat work folder’s .era/bin and adds it to that engine session’s PATH. An ordinary system terminal may not inherit it. Run era --help in an active Era chat; copying credentials from an old session is not a substitute for a new one.
Where do I create an Era MCP key?
Choose Create key on the Era server card under Apps → MCP on web or desktop. The full key is shown once; put it in your client’s authentication settings. Rotating the key stops clients using the old one.
Which MCP URL should I use?
Use the one address on the Apps → MCP export card: /api/mcp (server name era). Connect with a browser sign-in (OAuth) or an x-api-key / Bearer key; the address gives Era’s named tools by itself.
Why are not all MCP tools visible in my client?
The tool list depends on the key owner’s current role, enabled modules and catalogue mode. The plain URL gives the named tools; ?tools=full requests the full action catalogue. Generated docs describe schemas, while live tools/list determines your actual access.
How do I give the CLI structured input?
Use --json @input.json for a file or --json - for stdin. Accepted arrays map to items for create/update/run/approvals and to ids for archive. Do not repeat the same field in flags and JSON; files reduce shell-quoting errors.
Why does --text not take my message?
Bare --text selects readable output. For a tool’s message text, use the JSON text field or --text="message". Default output is compact JSON; output mode and tool input are separate.
Should I repeat a CLI command after a connection failure?
Inspect the record or era turn report first. The CLI does not automatically retry; a disconnected write may have completed. For failed/partial results, identify completed items before deciding which remaining operation to retry.